-
Notifications
You must be signed in to change notification settings - Fork 0
Home
In a nutshell, signer node will watch for wrap and unwrap transactions on both ethereum and tezos, will sign given the signer key, and publish the result on IPFS.
Events are linked together: each event contains a link to the previous one, and the head of this log is published under an ipns key, specific to each quorum member. This ipns key serves also as the quorum member identifier inside the quorum contract.
Another peace of software, the indexer, is in charge of pinning signers events, as long as providing a convenient api for the dAPP. Anyone can run an indexer, but BenderLabs will maintain the official one, used by the dAPP.
The indexer is not mandatory to use $wrap protocol, it just helps a little bit.
Signer is written in F#, with .NET core.
It requires access to :
-
a tezos node. It was tested with an archive node, but it should be working with a full node
-
an ethereum node
-
an ipfs node, if possible with --enable-pubsub-experiment --enable-namesys-pubsub
-
a persistent file system
-
Requirements on CPU and RAM are fairly low (it fits on an aws micro instance)
Signer is available as a:
-
Self contained .net executables for several environments
Refer to Configuration to learn how to configure the signer.
Refers to setup guide to get started quickly
Signer node requires very little maintenance, still, refer to Operations to know more.