Post #14455

9c37df468da7dcc6e1db70ca3b280708079a0b3fdf880be0c68bdf03c82bab26
ca44e9aebcd7ca62bb616e862d87d9e620187080204c00f5752c8a9c4f805d2d
Signature not verified

This entry might be using an old signature, or it was signed by a key that does not exist on the server.

{"entry_date":1556192394,"post_data":{"edit_count":0,"last_edit_date":0,"last_edit_user_id":0,"message_sha512":"cc445f6a866f7e3592b55d8fe59eae18723bc5952820b776dd8f3803491d23947186d0ab0209e92527cb1a7bf52ac5fcac4d02debb7e91748a7308da02668cae","node_id":59,"post_date":1556191794,"thread_id":1885,"title_sha512":"d4b73ced94be9929a46f7d19625c142fcf4e32eb1a7e558837a5a7690f747dff6491095845798f05e6e9f4f65430febb25ccf4d961105066febdd69139165285","user_id":56},"post_link":"https:\/\/factomize.com\/forums\/index.php?threads\/1885#post-14455"}
The entry content as it exists in the database. This should be verified against the blockchain entry.
Q1 2019 Report
[B]Q1 2019 Report[/B]


[B]Website[/B]

In Q1 we finished the first overarching development cycle for the protocol website, completing testing, small bug fixing, and minor improvements throughout the website. We subsequently began our second overarching development cycle that began with the hiring of our new web developer, Greg Wolff, who has been great to work with this quarter. The first release for this second development cycle is the new factom ecosystem portal. As we go we continue to build out the developer portal, and we believe that this portal is becoming a fantastic resource for developers within the the factom ecosystem.

Ecosystem Page: [URL]https://www.factomprotocol.org/ecosystem[/URL]
Documentation Portal: [URL]https://developers.factomprotocol.org/[/URL]
Update: [URL]https://factomize.com/forums/threads/factomprotocol-org-second-major-version.1674/[/URL]


[B]FAT Protocol[/B]

The Factom Asset Token Protocol made huge strides in Q1 2019. This was the quarter that the FAT protocol was truly brought to life. Please read the below update thread for more information:
Update: [URL]https://factomize.com/forums/threads/fat-development-grant-2-update.1880/[/URL]


[B]Legal [/B]

DBGrow continues to play a part in the Legal committee, lending our insights and experience and helping manage key relationships. In Q1 DBGrow has taken a backseat for the majority of the work to Nikola and Shuang, lead by the consistent hard work of MattO. While DBGrow is taking a smaller role in the legwork for the legal committee, we continue to lend our experiance where needed, and absorb all of the information we can as it is absolutely critical to have members of this community be knowledgeable on legal matters surrounding the factom blockchain and ecosystem, and knowledge from the work within the legal committee continues to be essential when discussing the factom protocol with corporate and government entities.
Update: [URL]https://factomize.com/forums/threads/legal-research-working-group-update-jan-2019.1454/[/URL]


[B]Outreach[/B]

DBGrow continues to engage important parties about FAT and the Factom protocol. We believe that the impact of these meetings over time will be important, and will help contribute to a growing mindshare for the factom protocol with developers, companies, and government.


[B]Private projects[/B]

This section will cover all DBGrow work as well as co-ventures with other entities. In Q1 we have made exciting strides in our developments with clients and partners. We hope for Q2 and Q3 to be able to discuss this work more, and to see more projects go live on mainnet. We are very excited by where we stand right now.


[B]Looking ahead to Q2 2019[/B]

Q2 2019 will see a continued revamp and refinement to the factom protocol website, continued promotion such as the Odyssey Hackathon, continued outreach to important entities, continued work with clients/partners, finalization of the core of the FAT protocol, and plans to bring on new developers and delve into exciting new FAT protocol functionality to continue to push the boundaries of what is possible on the Factom Protocol.
This is the raw content, without BBCode parsing.
Top