5
3 years agoby fractaloopat difficulty 2

The underpinnings of Fabric will be based in distributed logic. Given the complexity of the topic, it makes sense to adopt a formalized logic to describe protocol behaviors. For example, the declarative language Bloom seems to provide a strong foundation upon which to construct distributed protocols. The published paper has more details that help explain the necessary primitives.

2:2:sha3:20150729:00440069007300740072006900620075007400650064002000700072006f0074006f0063006f006c0020006c006f006700690063::uixxd:185

For now, we require a user account to participate.

Heads up!

Registering won't immediately log you in — you'll need to do so manually. If you want to fix this, check the official GitHub issue for this problem.

We'd also like a plugin to support <keygen>, or just cryptographic identity in general! If only we could do it without Javascript...

Only showing top-level comments. To see a thread, click "reply".
2
3 years agoby martindaleat difficulty 2

I deeply agree with the need for a formalized logic, if not at least a grammar. I've begun to outline some of my thoughts on this in martindale/maki#79, which is a necessary component for "service contract" representation to peers. I'm really leaning towards standardizing the ES6 class structure with a standard set of decorators and function names – but I'll be deferring that work unless someone else would like to take it on.

-2
3 years agoby chrisat difficulty 2

Needs more cats.

For now, we require a user account to participate. If you'd like to change this, look at martindale/converse#7.

Built with Maki and deployed to the Fabric network.

decentralize all the things.