-
Notifications
You must be signed in to change notification settings - Fork 9
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
Phase 1 logic #24
Comments
Missing in description above - step 8) confirmHosting has an additional index parameter to identify which encoding is being confirmed. |
jam10o-new
pushed a commit
that referenced
this issue
Jun 16, 2020
also, changes described in point 13 have been implemented |
(for me) new spec: https://github.com/ninabreznik/service.js/blob/dev/src/simulate-substrate.js |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
@todo
1. publisher registers new data
we get merkle root like this https://pastebin.com/QH7egWUX and then submit it to the chain
2. chain emits
SomethingStored
event3. after the event is emitted, users can register for different roles: encoder, hoster, attestor
4. When users registers for any of the roles, chain will check if there is any data that needs hosting and if there is at least one hoster, one encoder and one attestor, then 'New Pin' is emitted
5. new event is emitted (
NewPin
) where encoder and hoster are notified about what feed needs hosting/encoding6. we pair hoster and encoder: encoder compresses data and passes them over to hoster
7. when encoder finishes its job, it notifies the chain (registerEncoding)
8. when hoster gets all the data, it also notifies the chain (confirmHosting)
9. chain emits event:
HostingStarted
10. Publisher can now submitChallenge
11.
Challenge
event is emitted where hoster is notified about the challenges12. Hoster submits proof to the chain
13. If challenges are successful, chain emits new event:
AttestPhase
14. random attester is selected to go grab data from the swarm
15. Attester reports back to the chain (submitAttestation)
The text was updated successfully, but these errors were encountered: