Search results

  1. Mitchell Berry

    Amendment Doc 107

    Indeed, this whole proposal is that the opportunity should be there for anyone who wants to submit early. Or even draft grants that can be discussed without fear or favour. People can always submit grants 10 minutes before the deadline as exists now, opening up the period allows more time for...
  2. Mitchell Berry

    Amendment Doc 107

    I certainly agree for reasons of transparency and simplicity.
  3. Mitchell Berry

    Tracking [Factomize-8] ANO Promotion / Demotion System

    Which developer/s are working on this? Is it considered a FTE position for 3 months? So essentially on par with 480 hours of work done? Additionally interested if the development work funded by the community will be open sourced upon completion or will it remain the proprietary property of...
  4. Mitchell Berry

    Amendment Doc 107

    Spent an embarrassingly long time trying to simply move one column up so it's all in order as desired (feel free to laugh at the revision history). Couldn't work out the highlighting it in that particular texture of blue, can I leave that to someone more talented. It's almost as if we've...
  5. Mitchell Berry

    Amendment Doc 107

    I've updated it to 79 days for the discussion period anyway. Keen for other thoughts on the matter. Putting it out there.
  6. Mitchell Berry

    Amendment Doc 107

    So would 80/79 be acceptable without amending other parts of the doc?
  7. Mitchell Berry

    Amendment Doc 107

    Proposing a change to section 4.2 Changing both Grant round announcement by guides and Grant application discussion period starts to 80 days. Draft is here: https://docs.google.com/document/d/1t3iXTzrIP_svbj7PFvVsd1VyIHcMjvkaBTt3C5SqNuU/edit?usp=sharing Original...
  8. Mitchell Berry

    Early Grants

    Awesome, thanks guys. I've made a draft with the changes of 80 days for both announcement and discussion (as below). Will go through the motions and see what people think about it.
  9. Mitchell Berry

    Early Grants

    Is there anyway to submit grant proposals for the next grant round so that interested parties have more time to analyse the content and the future implications of the work being done? Struggling with the reasoning behind restricting it all to a certain window, I'd be interested in hearing the...
  10. Mitchell Berry

    [DBGrow-Factom-001] FAT Smart Contracts

    To extract some links for others: WASM Proof-of-Concept: https://github.com/Factom-Asset-Tokens/wasm-contract-poc Full research paper: https://docs.google.com/document/d/12HeGY7WePF9vaAg4CfQlmeseCOBeBgEvrOrE71Tu_w8/edit# PetriNet Event store: https://github.com/FactomProject/ptnet-eventstore...
  11. Mitchell Berry

    Tracking [Kompendium-4] Rust Client Library for the Factom Protocol

    Async was stabilised in rust today (was expected in 1.38 but had a few blockers) and the long-awaited futures 0.3 released yesterday with async support, but to be frank most of this delay was me and life commitments. Not going to shy away from that, there's preview crates available for both...
  12. Mitchell Berry

    Tracking [Kompendium-4] Rust Client Library for the Factom Protocol

    Just an update. Currently implementing : Some common traits to add easy interoperability with other libraries. Ongoing work investigating the best path forward for overhauling the test suite making it portable and easier to use, at the moment it requires downloading a small database and...
  13. Mitchell Berry

    Funded [Kompendium-3] Rust Client Library for the Factom Protocol

    Additonally: * Proper test harness. The current setup requires developers to use a custom db, devs shouldn't need to download a random blockchain on github to test. This can all be achieved using testnet and open nodes. * "had a few initial problems": I should really acknowledge a big thanks...
  14. Mitchell Berry

    Funded [Kompendium-3] Rust Client Library for the Factom Protocol

    Yes it currently returns a serde object which still requires some work from the end user. Planned work was cleaning up the futures runtime and allowing people to drop in alternatives, adding fully fledged response structs, better documentation, refactoring initial entry points into the client...
  15. Mitchell Berry

    Process Discussion Authority Node Operator Selection After Action Report

    Yeah it's gone off track and I'm certainly in some way responsible for that. I get some contributions can be intangible, the problem is that there's big promises while giving not much back. An infra node gives a lot back to the community via grants yet many people seem to see that as worthless...
  16. Mitchell Berry

    Process Discussion Authority Node Operator Selection After Action Report

    This is getting silly. Decentralisation is the goal for both node security, legal obligations and most importantly protocol integrity. I'm worried that the entire concept of the whitepaper is being handwaved away here with buzzwords. Absolutely do not think we should simply create more auth...
  17. Mitchell Berry

    Process Discussion Authority Node Operator Selection After Action Report

    (32 / 2) + 1 But upon reflection it's 30 ANO's and so only 16 servers that need to be corrupted isnt it? Guessing this means us at Kompendium. Andy is a Commander in the Marines and has recently been called up for deployment, he's away for a month with unspecified communication times, I get...
  18. Mitchell Berry

    Process Discussion Authority Node Operator Selection After Action Report

    Saying a respectable organisation who simply outsources the responsibility is putting the entire protocol at risk, can find you a sysadmin to work for a penny and they will happily roll and then inject malicious code for 2 pennies. The incentives currently exist to encourage prospective ANO's to...
  19. Mitchell Berry

    Process Discussion Authority Node Operator Selection After Action Report

    I think there's many decent things to glean from the writeup here, glad it's finally public. To summarise from the earlier wall of text: Truly struggling with the concept of getting people with zero experience administrating servers to go hire "random sysadmins" who have no incentive to...
  20. Mitchell Berry

    Process Discussion Authority Node Operator Selection After Action Report

    The social media consultants and marketing team should be running the servers instead, perhaps the ideas guy too :) Who would you call in the middle of the night to triage a downed server: The ideas guy or the sysadmin? Should the entire integrity of the protocol be outsourced to unconcerned...