Erwin Morrhey
Erwin Morrhey
Since the build-from-source introduction, our documentation lagged behind. This is a good time to restructure it. On the pyrsia.io website, we make a distinction between - Tutorials Which I would...
When a verify(payload) is called with a transaction payload (= transparency log) of operation add_node the verification service will: - lookup if the peer_id and public key were previously marked...
This umbrella issue is here to capture all missing blockchain things needed to support the 0.2 release. * call from TransparencyLog to Blockchain https://github.com/pyrsia/pyrsia/issues/1006 * make sure blocks are available...
This issues continues where #1006 stopped: when a new block is committed to the chain, the TransparencyLog has to know about it (e.g. an event listener) to it can store...
## Description - Add tutorial about building docker images from source - Include a --listen-only true command line argument for easier standalone demos Fixes #954 ## PR Checklist - [x]...
In the `add_artifact` of the TransparencyLog component, as a final step, it now stores the TransparencyLog. This must be changed to: - call the blockchain `add_block` method and wait for...
Since we do AutoNat bootstrapping by default, a locally started pyrsia node is automatically connected to the 'Pyrsia network'. As a result, I've found that when connected to the central...
The blockchain component itself will need access to stored blocks (e.g. to make them available in the p2p network). Therefore the Blockchain component itself will be responsible for storing blocks....
Pyrsia is building official docker images on demand (#1004) (which is fine for milestone 0.2) but in the end, we need to have a mechanism that makes sure to build...
Setup mechanism to make sure new (version of) official docker images are build in the Pyrsia network
In issue #1003 we made sure (a subset of) official docker images were built in the Pyrsia network. We should now also setup a mechanism to keep on par with...