Re: Agreements Network Update

Silas Davis
 

Hi André,

Thanks for the heads up on the document - this should be fixed now.

Regarding T5 - we had an operational glitch caused by an underlying bug
with Burrow's state versioning across restarts. As a result of some
maintenance work some months ago this took down a couple of our nodes (and
other network nodes). To fix this a special build of Burrow was needed, the
content of which is in this commit:
https://github.com/hyperledger/burrow/commit/a995c0cf27af30be22f96ac1d6b84b49e46d49ae

If you would like to catch up a fresh Burrow node on current T5 you will
need to run this special build, you can build of:
https://github.com/hyperledger/burrow/tree/v0.23.3-stutter. A docker build
is available here: quay.io/monax/burrow:v0.23.3-stutter.

Apologies the communication about this was not better - we did a hotfix
over Christmas and were focussed on the core stability of our validator
pool to keep T5 up and running.

Silas

On Thu, 10 Jan 2019 at 15:28, André Simeit via Lists.Agreements.Network
<mail=mailhost.xyz@...> wrote:

Hello,

the download links at https://docs.agreements.network/#boot-burrow don't
work.

I could get the files from


https://raw.githubusercontent.com/agreements-network/docs/staging/burrow.toml


https://raw.githubusercontent.com/agreements-network/docs/staging/genesis.json

Before starting the new burrow the old data/blockchain-directory had to
be deleted, otherwise burrow would not start.

After starting I noticed some errors in the log like these:

{"addr":"dd2067d02dab9c25ac157f98ec9683972f08599b@...:26656
","caller":"switch.go:365","component":"Tendermint","err":"auth
failure: handshake failed: unmarshal to p2p.DefaultNodeInfo failed after
3 bytes (invalid typ3 bytes
\u003cInvalid Typ3 4\u003e): "log_channel":"Info","message":"Error
reconnecting to peer. Trying

again","module":"p2p","run_id":"ca6fd7eb-14de-11e9-8d08-8e4bfb67c5b","scope":"tendermint.NewNode","time":"2019-01-10T13:53:44.342876733Z","tries":2}
{"address":"b1ffb9364c5b8e981d16fdf05084c8185218f24e@...:26656
","caller":"switch.go:558","component":"Tendermint","log_channel":"Info","message":"Dialing

peer","module":"p2p","run_id":"ca6fd7eb-14de-11e9-8d08-e8e4bfb67c5b","scope":"tendermint.NewNode","time":"2019-01-10T13:53:45.771664156Z"}

I'm not sure if everything works as it should.

Is there a way to see if burrow runs as expected?

regards,

André


Am 09.01.19 um 23:47 schrieb Adam Locklin via Lists.Agreements.Network:
Hello Agreements Network,

I hope everyone is off to a good new year. Monax Industries has been busy
building the Agreements Network (AN) and more! If you have a question on
the update below please reply to this email. AN update:


1.

Testnet 5 live, download here
<https://github.com/agreements-network/docs>, boot and sync your
nodes.
Documentation <https://docs.agreements.network/>.
2.

Testnet 5 is feature complete at the smart contract level so please do
feel free to stress test it and start prototyping your solutions.
3.

Initial AN token economics review is underway.
4.

Join and share AN Telegram <https://t.me/Agreements_Network> as we’d
like to get more discussion on legal tech, small businesses, artists
and
entertainers use cases.
5.

Open-sourced Blackstone
<https://github.com/agreements-network/blackstone> codebase, a
collection of smart contracts and RESTful APIs which together form the
basis for the AN. This is very probably the largest active smart
contract
repository in open source, so feel free to “mine” it for insights.
6.

To see the AN in action through the Monax Platform, please sign up
here
<https://monax.io/platform/> for a demonstration or reach out to me,
@adamlocklin
7.

If you have a minute, we developed a guessing game with legal
agreements, smart contracts, and executing on a blockchain (yeah we’re
nerds) https://app.monax.io/marmota-prime You can play daily until
February 2nd, Groundhogs Day with all prizes go to charity for
children.


Sincerely,

Adam Locklin




Join main@lists.agreements.network to automatically receive all group messages.