mirror of
https://github.com/IT4Change/gradido.git
synced 2025-12-13 07:45:54 +00:00
add roles and iota colored coins
This commit is contained in:
Einhornimmond
parent
32205dc798
commit
27982f558b
53
docu/Concepts/Snippets/1-Blockchain/Roles.md
Normal file
53
docu/Concepts/Snippets/1-Blockchain/Roles.md
Normal file
@ -0,0 +1,53 @@
|
||||
# Roles
|
||||
User Roles also handled by blockchain and node servers
|
||||
|
||||
My Goal is to save not only the gradido transactions in blockchain but also
|
||||
who is allowed to create new gradidos,
|
||||
who allow joining new user to the group,
|
||||
who allow connect to another group and
|
||||
how the community decide which one is allowed to do this things.
|
||||
|
||||
## Why?
|
||||
If this would be handled only by community-server everyone could be easly
|
||||
overwrite this rules by using a modified client to send his transactions direct over
|
||||
hedera or iota bypassing the community-server rules.
|
||||
With hedera it is possible to only allow sending messages to a topic with the correct admin key,
|
||||
but then is the admin the single point of failure. Also must the key saved on server to allow everyone
|
||||
sending gradidos or the transactions will only be proccessed, when admin is logging in.
|
||||
If we don't use blockchain technologie at all, we have a big single point of failure.
|
||||
The Community-Server and everyone who has direct access to server and the admins of course.
|
||||
But it would be much much simpler of course :)
|
||||
|
||||
In summary it is to make sure that the community is in power and no one can take over.
|
||||
|
||||
## How?
|
||||
There is a special type of transactions with which users determine who can determine what.
|
||||
This transaction control which signatures are neccessary for things like creation and so one.
|
||||
For this I think different types are needed.
|
||||
- *one*: The founder of group (or someone other choosen) decide everything, this is default from start
|
||||
- *some*: a number of user must sign, set absolute count or relative count
|
||||
- *most*: more than 1/2 or 3/4 must sign
|
||||
- *all*: all member must sign, default for choose which mode will be used
|
||||
- *one-council*: one member of council
|
||||
- *some-council*: absolute or relative number of council members must sign
|
||||
- *most-council*: more than 1/2 or 3/4 from council members must sign
|
||||
- *all-council*: all members of council must sign
|
||||
|
||||
this configuration can be done for different types of action,
|
||||
so the voting-mode for creation may differ from voting mode for
|
||||
add new members to community. Also the council members for different actions
|
||||
may differ.
|
||||
Also how to vote for council members is an extra type of action.
|
||||
|
||||
## Veto
|
||||
Especially for *some* and *some-council* maybe also for other types.
|
||||
The users there could vote but haven't yet and not all need to vote,
|
||||
can make a Veto with Explanation which reset all existing signs of current vote,
|
||||
and is needed to sign by all which again vote for the case.
|
||||
|
||||
## Summary
|
||||
With that setup all community consense models should be possible except Democracy.
|
||||
Democracy needs a secret ballot. The votes on blockchain are open (at least if someone knows which
|
||||
public-key belongs to which user). A secret ballot on blockchain is really hard. By my last
|
||||
recherche I haven't found on. But maybe this can do the trick: https://secure.vote/
|
||||
|
||||
34
docu/Concepts/Snippets/Iota/ColoredCoins.md
Normal file
34
docu/Concepts/Snippets/Iota/ColoredCoins.md
Normal file
@ -0,0 +1,34 @@
|
||||
# Wie Colored Coins in Iota funktionieren
|
||||
## Schöpfung
|
||||
- Colored Coins werden bei Iota mit einer speziellen Transaktion erzeugt
|
||||
- Die Farbe des neuen Coins wird durch den Transaktionshash beschrieben
|
||||
- Die einmal erzeugte Menge von Colored Coins ist fest
|
||||
- Um die Menge zu erhöhen müssten neue Colored Coin erzeugt werden und die alten damit ausgetauscht werden (z.B. mittels SmartContract)
|
||||
|
||||
## Geldmenge
|
||||
- Colored Coins basierend auf den normalen Iota-Coins somit werden soviele Iota-Coins benötigt wie man Colored-Coins braucht
|
||||
- 2.779.530.283.000.000 Iota maximale Coinmenge
|
||||
- Weltbevölkerung 2021: 96.954.663
|
||||
- Pro Kopf Geldmenge Gradido: 53.476
|
||||
- Benötigte Iota Coins für Gradido mit 4 Nachkommastellen mit 25% Puffer:
|
||||
- 96.954.663 * 53.476 * 1.25 = 6.480.934.448.000
|
||||
- Es sind genügend Iota Coins vorhanden im die ganze Welt mit Gradido auf Basis von Iota versorgen zu können
|
||||
|
||||
## Kosten
|
||||
- Kurs am 30.08.2021: 1 Miota = 0,84
|
||||
- Bei Verwendung von 4 Nachkommastellen braucht es 10 Miota für 1.000 Colored Coins (Gradido) also Miota im Wert von 8,40€
|
||||
- Aktuell (30.08.2021) geschöpfte Gradido Cent: 17.001.990.500
|
||||
- Notwendige Miota: 17.002.0, Wert: 14.286,73 €
|
||||
- Solange die Benutzer Kontrolle über ihre Keys haben können sie mit einem regulärem Iota Wallet die Gradidos wieder in Iota umwandeln (um z.B. der Vergänglichkeit zu entgehen)
|
||||
- Mit 2 Nachkommastellen wird die Vergänglichkeit schon bei 100 Gradido und 1 Stunde ungenau
|
||||
- 1 Stunde, 100 Gradido, Vergänglichkeit: 0,00576, Gradidos nach einer Stunde: 99,99424 GDD
|
||||
- 1 Minute, 100 Gradido, Vergänglichkeit: 0,000096, Gradidos nach einer Minute: 99,999904 GDD
|
||||
|
||||
## Dust-Protection
|
||||
- Iota erlaubt bei leeren Adressen nur Transaktionen von mindestens 1 Miota
|
||||
- Nachdem 1 Miota da ist sind bis zu 10 Transaktione < 1 Miota erlaubt, bevor ein weitere Transaktion mit mindestens 1 Miota eingehen muss
|
||||
- Bei Verwendung von 4 Nachkommastellen entspricht das 100 GDD, bei 2 Nachkommastellen 10.000 GDD
|
||||
|
||||
|
||||
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user