* Remove bootstrap peer (#189)
* Change bootstrap servers to DHT-only peers (#187)
* support voucher file-based claims (#183)
* Change bootstrap servers to DHT-only peers
Changing my bootstrap servers to DHT-only peers with somewhat lower
specs. One of the new ones is in the US and the other one is in
Switzerland. Both use reliable providers and have 10Gbps network
interfaces.
---------
Co-authored-by: Cassandra Heart <7929478+CassOnMars@users.noreply.github.com>
* Don't run self-test in DHT-only mode (#186)
* support voucher file-based claims (#183)
* Don't run self-test in DHT-only mode
The node tries to create a self-test when ran with the `-dht-only`
flag, but it doesn't load the KZG ceremony data in DHT-only mode
which leads to a crash.
Don't run self-test when the `-dht-only` flag is set.
I tested by starting a node locally with and without existing
self-test and with the `-dht-only` flag.
---------
Co-authored-by: Cassandra Heart <7929478+CassOnMars@users.noreply.github.com>
* Embed json files in binary (#182)
* Embed ceremony.json in binary
* Embed retroactive_peers.json in binary
* Signers build and verification tasks (#181)
* add signers specific Taskfile
* add verify tasks
* move signer task under signer folder
* create docker image specific for signers
* map current user into docker image and container
* ignore node-tmp-*
* add verify:build:internal
* prevent tasks with docker commands from being run inside a container
* rename *:internal to *:container
* add README.md
* add pem files to git
* Updating Q Guide link (#173)
* Update README.md
Updated link to Quilibrium guide to new website
* Update README.md
* feat: network switching and namespaced announce strings/bitmasks (#190)
* feat: network switching and namespaced announce strings/bitmasks
* bump version name and logo
* feat: mini pomw proofs as part of peer manifest (#191)
* shift default config directory under current folder (#176)
* feat: signature check (#192)
* feat: signature check
* adjust docker command so it doesn't invoke sigcheck
* remove old version
* add binaries and digests
* fix bug, revert build
* shasum has weird byte at end
* proper binaries and digests
* Signatory #13 added
* Signatory #3 added
* Signer 4 (#194)
* Signatory #5 added
* Signatory #9 added (#195)
* Signatory #1 added
* added sig.6 files (#196)
* Signatories #8 and #16 added
* Signatory #12 added
* Add signature (#197)
* reset build for v1.4.18 after testnet bug
* updated build, resigned by #13
* Signatory #16 added
* added sig.6 files (#198)
* Signatory #8 added
* Signatory #17 added
* Signatory #1 added
* Signatory #7 added
* Signatory #4 added
* Signatory #14 added
* remove binaries, ready to ship
---------
Co-authored-by: littleblackcloud <163544315+littleblackcloud@users.noreply.github.com>
Co-authored-by: Agost Biro <5764438+agostbiro@users.noreply.github.com>
Co-authored-by: Marius Scurtescu <marius.scurtescu@gmail.com>
Co-authored-by: Demipoet <161999657+demipoet@users.noreply.github.com>
Co-authored-by: 0xOzgur <29779769+0xOzgur@users.noreply.github.com>
Co-authored-by: Freekers <1370857+Freekers@users.noreply.github.com>
* And what country can preserve its liberties if their rulers are not warned from time to time that their people preserve the spirit of resistance?
* adjust check to handle peer id change
* add version label and trim repo url
* add README for protobufs
* add version to NodeInfoResponse
* add docker login task
* remove version from docker compose file
* return version with GetNodeInfo response
* add basic -node-info flag
* print max frame as well with -node-info
* expand protobuf README
* update node command examples to use node binary and make log commands follow
* return all of NodeInfo
* extract FormatVersion
* print version of running process
Adds two new bootstrap peers on dedicated servers both with 16 core Cpus and 32/64GB Ram. The first one is in the US and the second is in the EU. The first one is at Oneprovider and the second one is at Worldstream.
Adds two new bare metal bootstrap peers both with high end AMD cpus and 128GB ram. The first one is in the US and the second is in the EU. The second one is at an untested new provider.
* move to a message processor channel model for ceremony
* switch to goroutine
* readjust
* cut down volume
* keep distance data asserted
* bring it back so more bootstrap nodes can exist
* bump the version, it's go time
* Modify the wrong default volumes value to /root/.config (#109)
* move extract version logic to new version.go in config package
* update version extraction command
---------
Co-authored-by: talentbuilder <talentbuilder@163.com>
