Post #31321

39c531bd8491d39f5855c3a69f6339f1d622fbe1771879cdf7e3f6c0249463e8
73e420556ba0a62f0ec3a2adc9a03d77fc90d13832738e2c9822d2f530f7e42f
e2c61429397da55a5ee7749088023feb12e0e8e261dfeba32ee7c0794f9a12f8
Signature verified

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

{"entry_date":1610814019,"post_data":{"edit_count":0,"last_edit_date":0,"last_edit_user_id":0,"message_sha512":"b8b30b9cbbbdf32709dc5adf982c425b1219e85146d17a7180e9cfee747fa48bf04b4eac886436270f3790949b29e071f29c4297cf17fc8420a9a49271a02c36","node_id":52,"post_date":1610814019,"thread_id":5633,"user_id":22},"post_link":"https:\/\/forum.factomprotocol.org\/threads\/proposed-factom-roadmap-for-2021.5633\/post-31321"}
The entry content as it exists in the database. This should be verified against the blockchain entry.
Proposed Factom Objectives
I do think it’s a positive to put this out there and simply label it “what we’re working towards” or “soft objectives” rather than we “will complete all this things to production grade.”

We can discuss and design all these features in 2021, so that is progress.

Jason, it’s simply describing this a bit differently to what is feasible.
This is the raw content, without BBCode parsing.
Top