Post #31395

e81a4b0c081090804aa7dce1ecc436f1ebd31bf3d3ea06fa1b84a3a930b9b734
f51a1c9ece9a134c63028955820ca35a4872203a600b454d47459c5ae433e9aa
e2c61429397da55a5ee7749088023feb12e0e8e261dfeba32ee7c0794f9a12f8
Signature verified

The signature from the blockchain entry has been verified against an identity on this server.

{"entry_date":1611159681,"post_data":{"edit_count":0,"last_edit_date":0,"last_edit_user_id":0,"message_sha512":"1dd84a660513e2d26a0f2b19b0c805e1904e302133d4c082e452f2f6f5ecb1c3273d277ac638147086eefd2bd264306c3b9cbe195feaedb916e59a76c3b0d717","node_id":52,"post_date":1611159681,"thread_id":5637,"user_id":8},"post_link":"https:\/\/forum.factomprotocol.org\/threads\/batched-amendment-strategy-and-resource-director-proposal.5637\/post-31395"}
The entry content as it exists in the database. This should be verified against the blockchain entry.
Batched Amendment - Strategy and Resource Director Proposal
roadmaps are a living document. It gets changed over time, especially in agile times like these. Obviously not every week or month, but priorities shift if something takes of for instance or doesn't seem to work. That is part of the game. On of the biggest mistakes though is trying to communicate a really elaborate roadmap with many things in there. They you are setting yourself up for (perceived) failure, because the chances of underdelivering are very big.
This is the raw content, without BBCode parsing.
Top