The coordinator is open source as of Nov 20, 2018. See this article: blog.iota.org/coordinator-part-4-an-open-source-coordinator-7d3804931058 The source code is on GitHub here: github.com/iotaledger/compass
Hi Mobilefish.com, a bit off the topic, could you share with us the type of font you are using in videos, it's close to Halifax but not quite? Thank you for great and clear presentations, kind regards
I am using Apple Keynote software to make my presentations. Thumbnail Title: Font Gill Sans (Bold) Subtitle (Green): Font Krungthep (Regular) Presentations Title: Font Font Gill Sans (Light) Boby: Font Font Gill Sans (Light)
What happens if someone attach to an address, the coo would use in future (index 800.000 f e.). Would the coo just skip this index number, as it' not zero, and an milestone number too?
The Coo creates milestones (= zero value transactions) which are signed. The Coo address is hardcoded in the IRI. Malicious nodes can not create fake milestones because the milestones are signed by the Coo.
Thanks for all those videos. Very nice. Just a little question : how is the milestone index transmitted ? I was thinking that it was using the obsolete tag, but obsolete tag can be modified to remove M in normalized bundle hash. Is it still safe to use the obsolete tag to store the index ?
If you look in the iota.lib.js Javascript library the milestone is retrieved as follow: var latestMilestone = nodeInfo.latestSolidSubtangleMilestone; You can use the following API: iota.api.getNodeInfo. It makes no sense to use the obsolete tag to store the index if you already know that it might be modified to remove M.
OK, but my point is how this index is discovered by the node. At some point, the fullnode receive a tx and detect that this tx is a milestone because it is signed by the coo. So far so good. Now the node must discover the index of this milestone. Where is it ? in the obsolete tag ?
The coordinator is open source as of Nov 20, 2018. See this article: blog.iota.org/coordinator-part-4-an-open-source-coordinator-7d3804931058
The source code is on GitHub here: github.com/iotaledger/compass
Hi Mobilefish.com, a bit off the topic, could you share with us the type of font you are using in videos, it's close to Halifax but not quite? Thank you for great and clear presentations, kind regards
I am using Apple Keynote software to make my presentations.
Thumbnail
Title: Font Gill Sans (Bold)
Subtitle (Green): Font Krungthep (Regular)
Presentations
Title: Font Font Gill Sans (Light)
Boby: Font Font Gill Sans (Light)
Mobilefish.com thank you
Do you think that the coordinator can be removed one day ?
Yes, it will happen! The coordinator is also a botttleneck.
What happens if someone attach to an address, the coo would use in future (index 800.000 f e.). Would the coo just skip this index number, as it' not zero, and an milestone number too?
The Coo creates milestones (= zero value transactions) which are signed.
The Coo address is hardcoded in the IRI.
Malicious nodes can not create fake milestones because the milestones are signed by the Coo.
Its as good as impossible that this will ever happen
Thank you very nice technical info
Thanks for all those videos. Very nice. Just a little question : how is the milestone index transmitted ? I was thinking that it was using the obsolete tag, but obsolete tag can be modified to remove M in normalized bundle hash. Is it still safe to use the obsolete tag to store the index ?
If you look in the iota.lib.js Javascript library the milestone is retrieved as follow:
var latestMilestone = nodeInfo.latestSolidSubtangleMilestone;
You can use the following API: iota.api.getNodeInfo.
It makes no sense to use the obsolete tag to store the index if you already know that it might be modified to remove M.
OK, but my point is how this index is discovered by the node. At some point, the fullnode receive a tx and detect that this tx is a milestone because it is signed by the coo. So far so good. Now the node must discover the index of this milestone. Where is it ? in the obsolete tag ?
Thank you!
COORDICIDE!!!!