Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - wackou

Pages: 1 2 [3] 4 5 6 7 8 9 10 ... 33
BitShares PTS / Re: down
« on: July 13, 2016, 08:19:01 pm »
that's a good question, but I'm not sure how to get you voted in... I know that there was some trick done when we switched from the old pts to the new dpos-pts, but I don't remember exactly what it was. This was done because there were only 10 people volunteering at the time, so we had to ensure that they were all active delegates (so each of those 10  volunteers got 10 delegate spots).

Recently, there have been only 6 active out of those 10, so 60% delegate participation, which is quite close to getting a network that dies... New blood would be welcome for sure!

Maybe you should ask [member=20744]cube[/member] (he was organizing a lot) or [member=94]pc[/member] (he update pts to dpos-pts using the code from bitshares), they might know more about it.

General Discussion / Re: Bitshares Allstars Initiative: Final Phase
« on: July 11, 2016, 11:27:59 am »
Had to mention [member=21903]roadscape[/member], was surprised he wasn't already on the list!

DAC PLAY / Re: any update?
« on: June 14, 2016, 03:52:57 pm »
[member=1744]logxing[/member] any comment on whether we should upgrade or not? Is it the final release?

DAC PLAY / Re: any update?
« on: June 13, 2016, 10:30:55 am »
this page here:

states that there's gonna be a hardfork in less than 2 days... However it hasn't been announced anywhere. Should witnesses (err, delegates) upgrade?

General Discussion / Re: !!!CAUTION!!! All public seed nodes down??
« on: June 10, 2016, 03:24:24 pm »
Shouldn't we build more nodes using the fund accumulated by "refund" worker?

Either this, or ask witnesses to provide a seed node on top of the witness node, and vote out those who don't.

If the first case, then I would also fund Thom, who's been providing 4 seed nodes for a long time now without any sort of compensation.

General Discussion / Re: !!!CAUTION!!! All public seed nodes down??
« on: June 10, 2016, 10:55:18 am »
thanks guys on the quick reaction time!

[member=11]dannotestein[/member] are you the one in charge of the following seed nodes?

if not, do you happen to know who is?

General Discussion / Re: !!!CAUTION!!! All public seed nodes down??
« on: June 09, 2016, 03:00:49 pm »
there are quite a few seed nodes down or stuck again...

[member=22138]lafona[/member] [member=9301]puppies[/member] [member=4564]betax[/member] [member=10831]liondani[/member] [member=20744]cube[/member] [member=2186]iHashFury[/member] [member=34]Harvey[/member]

General Discussion / Re: !!!CAUTION!!! All public seed nodes down??
« on: May 23, 2016, 07:28:50 pm »
Please add my primary seed node to your list.

Hm... it should get added automatically, eventually. Provided that it is well-connected itself, and accepts connections.

Strange - my node is up and has been for some time according to

Why is it strange? I ran all of my nodes on port 1779 for months and they always had between 40 and 60 connections each, despite them not being advertised. Now that they're running on port 1776 I get closer to 100 connections on each node.

Apparently the nodes have a way of finding each other. Also, for whatever reason, all 4 of my nodes have not experienced the "stuck" state for a full week now.

iHashFury's node should get added with time as pc mentioned, as I guess his crawler hasn't been running for too long on the bitshares network and hasn't had the time to map the entire network yet. I believe there are more nodes in the bitshares network than the ~10 nodes on pc's page. Give it some time :)

As for you, Thom, what happened is that your nodes are declared to be on port 1776 in the official list of the bitshares client (see
When they were running on port 1779 they were not acting as seed nodes and so were "just" full nodes. Now that you are on port 1776 you get connected to as seed nodes by people starting the client, hence the higher number of connections I guess.

General Discussion / Re: !!!CAUTION!!! All public seed nodes down??
« on: May 06, 2016, 05:37:30 pm »
A view of the status of all seed nodes can be seen here:

As you can see, the situation is pretty dire, so let's make this a wake up call:


General Discussion / Re: !!!CAUTION!!! All public seed nodes down??
« on: May 06, 2016, 05:25:28 pm »
Here is the first few lines in my config.ini file. I see no reason why it should use port 1779 instead of port 1776:

# Endpoint for P2P node to listen on
p2p-endpoint =

# P2P nodes to connect to on startup (may specify multiple times)
#seed-node =
#seed-node =
#seed-node =
#seed-node =
#seed-node =
#seed-node =
#seed-node =
#seed-node =
#seed-node =
#seed-node =
#seed-node =
#seed-node =

As you can see the p2p-endpoint is defined to use 1776 and all of the seed definitions are built into the code, none are configured in the runtime config file. When I use netstat there are no listeners on 1776 but plenty on 1779, so the only conclusion I would be inclined to make is the definitions in the code must specify 1779 to override the p2p-endpoint defined in the config file.
You're starting with bts_tools right? [member=6601]wackou[/member] any idea?

yes, you should look into the "~/.bts_tools/config.yaml" file that defines the clients to run, not in the config.ini file. There you can add the "p2p_port" field set to 1776, eg:

Code: [Select]
        p2p_port: 1776

and restart your seed node for the change to take effect.

OpenLedger / Re: Thank you Ronny
« on: May 03, 2016, 08:48:23 am »

we need more posts like this! Let's stop arguing between ourselves when we all want the same thing, and recognize people such as Ronny that devote an incredible amount of energy to making this project successful. I agree with btswolf that the project wouldn't be the same without him.

Go Ronny!

I released bts_tools version 0.4 which adds support for publishing feeds for the ALTCAP asset!

See here:,19537.msg291276.html#msg291276

I do compute it from the average between what CoinCap and CoinMarketCap say, so it's slightly different than just CoinCap, let's see if that's an issue or not.

Released 0.4, here's the changelog:

Code: [Select]
0.4 (2016-05-01)

* API CHANGE: complete rework of the configuration system, please delete
  your old config.yaml file if you have any
* added full support for Steem, including feed publishing
* added feed publishing for BTS assets: TUSD, CASH.USD, CASH.BTC, ALTCAP
* added monitoring plugin that checks on the amount of free disk space
* fixed missed block notification for Graphene clients
* logs are now also present as rotating logfiles in the ~/.bts_tools folder

I posted a more lengthy post on Steem here:[member=6601]wackou[/member]/btstools-release-0

Hope you like it!

witness wackou and seed node updated to latest master

wanted to chime in, too :)

very interesting project, I will also update the bts_tools package to publish this feed and will publish it myself once I get around to do it. At the moment, I'm right in the middle of a refactoring + adding support for steem, so it'll take a couple more weeks I imagine, but you can count me in!

Pages: 1 2 [3] 4 5 6 7 8 9 10 ... 33