Search results

  1. Matt York

    Application idea for the Scientific community

    Don't mean to draw attention away form the original post, but posting here b/c it's directly relevant. I came acorss a project https://qri.io/ (pronounced: 'query') This project uses IPFS to store files (and so would be quite easy to anchor w/ factom) They provide several command line tools and...
  2. Matt York

    Factom 2.0: Breaking the Blockchain Barrier to Performance

    This is a fair criticism - I'd still point out that we can get rid of state. I look forward to the discussion of substrate in the other thread.
  3. Matt York

    Factom 2.0: Breaking the Blockchain Barrier to Performance

    Like any long-running project - Factomd has some technical debt. I think rust and other off-the-shelf components are compelling. However there's an underlying assumption that we cannot address the deficiencies in our codebase without throwing the whole thing away. I think this is a false...
  4. Matt York

    Factom 2.0: Breaking the Blockchain Barrier to Performance

    If we built a prototype on layer-2 that used the val-accumulator design (after all it's rooted in the layer2 DOE project) You could produce software that has alot of the same attributes being proposed by the full rewrite. In the long run this initial POC would itself still be useful on Factom...
  5. Matt York

    Factom 2.0: Breaking the Blockchain Barrier to Performance

    In my view a high TPS are new table stakes to 'be a blockchain'. @PaulSnow 's proposal actually simplifies the overall design of the system. What has held us back is trying to keep some of the things that are now being thrown out. As an engineer, sometimes deciding to throw a part of your code...
  6. Matt York

    Factom 2.0: Breaking the Blockchain Barrier to Performance

    This is an exciting step forward!
  7. Matt York

    Network Restart Proposal: Feedback Requested

    The technical approach here seems like it could work in an ideal system - I think some of the challenges we have with the current codebase may prove problematic (though there is plenty of merit in moving to a more decentralized tooling) From my observation of the current process - the main...
  8. Matt York

    Maxing out a Factom network

    Interesting use of the raspberry Pi in your testing I've been thinking about what it would take to setup a large-ish cluster as a larger devnet/testnet. May be an interesting tool when trying to analyze larger network behavior.
  9. Matt York

    Maxing out a Factom network

    Thanks for providing a thorough analysis (as always) I guess hunting for channels that are being starved for work while others are overflowing would be one symptom we could look for. Sort of depressing that this doesn't feel like a new line of investigation - essentially this is what has been...
  10. Matt York

    Maxing out a Factom network

    Yes, seemingly - but a larger VPC will surely support more IO. The observation about the CPU is that we cannot force it to 100% utilization by loading it. it could also mean that there is just some aspect of the current design that is throttling... I think more careful benchmarking &...
  11. Matt York

    Maxing out a Factom network

    Inspired to post by the latest testnet results there are 2 observations about performance. 1. Factomd seems to be IO bound, maxing out a network will never max out the CPU of a single node. I take this to mean that there is still room to improve. 2. On mainnet - we don't see the expected # of...
  12. Matt York

    Leader Module - Wax rewrite (petri-net model)

    An updated on refactor of leader behavior: Currently: the Initial module was scaffolded and can demonstrate basic behavior. Long term objective: Extract leader behavior from its entanglement with the globally abused 'state' object. Several other modules need to be extracted/refactored in this...
  13. Matt York

    Proposal to remove the Guide position

    Leaving aside practical issues of governance or coordination. I've enjoyed communicating directly with @Niels Klomp and @Brian Deery in various scenarios. Regardless of the title, I think there is value in having a consistent set of people that can be called upon to represent the sentiment and...
  14. Matt York

    Leader Module - Wax rewrite (petri-net model)

    Working on Factomd rewrite 'Wax' in this branch https://github.com/FactomProject/factomd/tree/FD-1225_wax_rollup During this phase of the project - we've been installing an internal pub/sub mechnism to allow different parts of the application to scale independently. (as a step on the roadmap...
  15. Matt York

    Process Discussion Core committee formation

    I'm interested in joining the core committee. I feel that I've been working on the factomd codebase long enough to have a good handle on some of the technical planning and requirements. I'm also interested in how current and future core features can support layer 2 development efforts --...
  16. Matt York

    HashnStore: Q2 2019 Update

    Working on the FAT report recently gave me some context and better language to be able to describe this a bit better - I should try to capture some of this in writing. I did an older POC for an auction - the technique I was using has changed a little so I'll try to re-implement this as a POC...
  17. Matt York

    HashnStore: Q2 2019 Update

    Ethereum + Factom comparison is interesting, would love to participate in discussion. One of the hurdles we face is that the Ethereum model is the dominant view of what a 'Smart Contract' is. So we are always looking for new ways of explaining the difference between that on-chain approach vs...
  18. Matt York

    GoLand IDE formatting configuration

    I wanted to document something I learned from @Clay Douglass this morning: I was using Goland w/o this setup and so some of my commits were always loading as modified on Clay's machine. It seems that I never configured my IDE to enforce formatting in the same way that previous factomd...
Top