-
Notifications
You must be signed in to change notification settings - Fork 338
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Postage stamps #1440
Labels
Comments
Closed
architecture proposals:
|
This was referenced Apr 6, 2021
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Epic
Story
Background
Swarm can be compared to a public harddrive, to which everybody can read and everybody can write. Looking at the Swarm network this way, there arises an obvious question: what information will be stored in this network and what information not?
In order to increase the utility of the network, node operators want to persist information that is most valuable for the uploaders. Uploaders can signal how much the chunk is worth to them by attaching a postage stamp to the chunk.
A postage stamp is created by burning BZZ on the main-chain (see smart-contracts). By burning tokens, we align the incentives of BZZ token holders with node operators. It is envisioned that later, postage stamp inpayments are not burned, but distributed to node operators.
Meeting notes, explaining technical architecture behind how postage stamps are implemented
Youtube video, explaining Swarm incentives (among them postage stamps)
Live demo at the Liberate Data week
Status
✅ Postage stamps contracts implemented
✅ API-endpoints ready on the
storage-incentives
branch✅ Use postage stamps in the Bee node
✅ Integration tests of postage stamps (#129), (#133)
🔨 bee-js team will work on making it easy to upload with postage-stamps
The text was updated successfully, but these errors were encountered: