Document Polls should include URLs

[abliss]

Otherwise how are we to know what we are voting on? Is there assumed to be an out-of-band means to distribute the documents?

E.g. I see that there are already 3 document polls outstanding; where do I find the document that hashes to cb1f81e42b5e75f000f94fc71a3ea70cab4bfc6f236b91e717f1b9516e5596b5 ?

[Fang-]

I see that there are already 3 document polls outstanding

The first one, with the weird hash (starts with 123456789, ends with a date), was a testing poll, and will likely time out without achieving majority.

The other ones (that actually got majority) have to do with the conditions that the Conditional Star Release was configured with. The hash is the keccak-256 hash of the following string:

The document value "0x0000000000000000000000000000000000000000000000000000000000000060" represents the claim that Azimuth and Ecliptic are live on the Ethereum blockchain and comprise the Urbit Constitution. The document value "0x00000000000000000000000000000000000000000000000000000000000000a0" represents the claim that Tlon has designated Arvo (the Urbit operating system, as described at https://urbit.org/docs/arvo/internals/) as "stable". The document value "0x00000000000000000000000000000000000000000000000000000000000000e0" represents the claims that (i) Tlon has designated the Urbit Network as having reached "continuity" ("continuity" means that there is a reasonable expectation that the Urbit Network can continue indefinitely without hard forks); and (ii) The Urbit Network has been confirmed to be secure by an independent third-party security audit.

The idea is that the Senate will generally inform each other of the contents of proposals out-of-band, but I agree there should be a central place to find and read documents that have achieved majority. We're still working out what the right way/place is.

[abliss]

Actually, now that I think about it, why include document polls in the ETH layer at all? Couldn't it be implemented in 5 lines of Hoon, rather than 60+ lines of Solidity in the trusted PKI kernel?

[philipcmonk]

The galactic Senate can make decisions about the Azimuth layer, so it makes sense where possible to keep that all within the same layer. Azimuth doesn't really depend on Urbit even existing. Also, we already had to have similar logic for Ecliptic upgrades, so we might as well keep it all in the same place.

…

On Tue, Jan 15, 2019, 05:38 Adam Bliss ***@***.*** wrote: Actually, now that I think about it, why include document polls in he ETH layer at all? Couldn't it be implemented in 5 lines of Hoon, rather than 60+ lines of Solidity in the trusted PKI kernel? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#4 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AFS8GPqC-MA-Y3GwhaYhR1Cek0eXS9xOks5vDdnvgaJpZM4aAUoa> .

[baudtack]

Given there is currently a current proposal that I can't find the text of... this is probably something to revisit.

[abliss]

@baudtack for reference, the current proposal is here: https://gist.github.com/abliss/d5e938b549880999d354f0be3d9d6bdb
See also https://master-malwyl.cypher.host/apps/coup for background.