BitShares Forum

Main => Stakeholder Proposals => Topic started by: pc on October 29, 2015, 09:19:17 pm

Title: [Witness] cyrano
Post by: pc on October 29, 2015, 09:19:17 pm
BitShares Witness Proposal - cyrano

My name is Peter Conrad, and I propose to run a BitShares witness.

Previous experience

I have followed the BitShares project since the early days of ProtoShares, back in November 2013. Since March 2015 I've been elected as a worker delegate in in the old (pre-2.0) BitShares blockchain. See my old proposal and some details on my technical background (https://bitsharestalk.org/index.php/topic,13995.msg181966.html#msg181966).

I have participated as a witness in the beta runs of the Graphene network. My witness node was up and producing blocks in BitShares-2.0 a few hours after launch. This directly proves my first-hand experience in running a witness. During the first two weeks of BitShares-2.0 my witness has signed more than 13,000 blocks, missing only 46 - more than 99.5% reliability.


Technical details

The witness node is running on a dedicated server in eastern Germany. The machine has 16G RAM and a mostly idle CPU - there's plenty of room for higher TX loads. The data center has high-speed fiber-optic links to interconnection points all over europe, resulting in an average latency of 300ms to my 30 (as of 2015-10-27) co-witnesses.


Please vote!

If you find that convincing, please vote for witness cyrano!
Title: Re: [Witness] cyrano
Post by: xeroc on October 29, 2015, 09:46:33 pm
+1
Title: Re: [Witness] cyrano
Post by: pc on May 15, 2016, 12:20:37 pm
I have created a network crawler that collects all publicly connectible seed nodes. View the results at http://seeds.quisquis.de/bitshares.html) or use the DNS seed in your config.ini:

Code: [Select]
seed-node = bts.seeds.quisquis.de:1776
And please don't forget to vote for my witness 'cyrano'... :-)
Title: Re: [Witness] cyrano
Post by: xeroc on May 15, 2016, 12:28:52 pm
Very nice .. wanted fo something similar for ages ..

How are you doing it? Custom DNS server or just updating zones regularily?

Would you want to host this on a bitshares.eu or bitshares.org domain?
Title: Re: [Witness] cyrano
Post by: pc on May 15, 2016, 02:39:07 pm
I ported the network_mapper from the old BitShares repo for the crawling.

The resulting data is transformed into HTML and zone files (for TinyDNS) using various scripts.

If you delegate a subdomain of bitshares.eu and/or bitshares.org to my server I can publish the data under that name, too.
Title: Re: [Witness] cyrano
Post by: xeroc on May 15, 2016, 03:37:50 pm
What subdomain would you propose?

seeds.bitshares.eu
seed.bitshares.eu
pool.seeds.bitshares.eu  (my favorit)

I have recently looked into http://gdnsd.org/
which looks very promising as it can do location-based resolution ..
Title: Re: [Witness] cyrano
Post by: pc on May 15, 2016, 09:41:00 pm
What subdomain would you propose?

seeds.bitshares.eu
seed.bitshares.eu
pool.seeds.bitshares.eu  (my favorit)

IMO one of the first two would be preferable, simply because they're shorter. :-)
But it's all the same to me.

I have recently looked into http://gdnsd.org/
which looks very promising as it can do location-based resolution ..

I'm always very sceptical about location-based resolution because the DNS infrastructure relies heavily on caching, and you never know how many caching recursive resolvers are sitting between the authoritative server and the client from which the query originates.
Title: Re: [Witness] cyrano
Post by: xeroc on May 17, 2016, 09:28:20 am
Good point .. i'll add the dns A records in a bit
Title: Re: [Witness] cyrano
Post by: pc on May 17, 2016, 03:43:56 pm
Good point .. i'll add the dns A records in a bit

Don't do that.

You must delegate the name to my server, with an NS record.
And add another NS record to ns2.afraid.org, they offer free backup DNS service. I'll set it up with them.

Like this, only for seeds.bitshares.eu instead of seeds.quisquis.de:
Code: [Select]
> dig ns seeds.quisquis.de

; <<>> DiG 9.9.6-P1 <<>> ns seeds.quisquis.de
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 48212
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1280
;; QUESTION SECTION:
;seeds.quisquis.de.             IN      NS

;; ANSWER SECTION:
seeds.quisquis.de.      11601   IN      NS      ns2.afraid.org.
seeds.quisquis.de.      11601   IN      NS      vblue.quisquis.de.

Title: Re: [Witness] cyrano
Post by: xeroc on May 18, 2016, 07:43:20 am
done :)
Can I simply delegate NS for seeds.bitshares.eu to ns2.afraid.org? I assume I need to set something up here so that they reply to seeds.bitshares.eu, dont't I?
Title: Re: [Witness] cyrano
Post by: abit on May 18, 2016, 09:36:03 am
Why not just add a CNAME record? NS is more heavy. For example:

Code: [Select]
seeds.bitshares.eu.      14400   IN      CNAME      bts.seeds.quisquis.de.
Title: Re: [Witness] cyrano
Post by: pc on May 18, 2016, 04:19:20 pm
done :)
Can I simply delegate NS for seeds.bitshares.eu to ns2.afraid.org? I assume I need to set something up here so that they reply to seeds.bitshares.eu, dont't I?

Oops, I didn't notice you're already using afraid.org for bitshares.eu. This is probably not going to work then.
I have switched to another secondary, please replace the ns2.afraid.org RR with puck.nether.net. No further action required on your side, everything is set up.

Why not just add a CNAME record? NS is more heavy.

I try to avoid CNAME, it usually does not quite what you think it does. (And it isn't more heavy, the client must generate two queries in either case.)
Title: Re: [Witness] cyrano
Post by: pc on May 27, 2016, 03:15:05 pm
The discussion about settlement parameters and BSIP-16 have brought to light what I consider a vulnerability in the implementation of SmartCoins aka MPAs. The discussion also shows that a significant portion of BitShares shareholders are willing to exploit that vulnerability and turn SmartCoins into a huge scam.

https://steemit.com/bitshares/@cyrano.witness/before-entering-into-a-smart-contract--read-the-fine-print

I do not participate in scams, therefore I have decided to stop publishing price feeds within the next 48 hours, regardless of the outcome of the proposal. I will resume publishing price feeds once said vulnerability has been fixed.