301
General Discussion / Re: Dry Run 8: Need for Speed
« on: July 14, 2014, 01:11:24 am »It is a good test of fork handling code
We should implement automatic firing of your delegate.
Yes, I concur. One block per delegate per round.
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.
Yes, I concur. One block per delegate per round.
302
General Discussion / Re: Dry Run 8: Need for Speed
« on: July 13, 2014, 11:03:20 pm »FOX is testing enabling the same delegate on two nodes to attempt to fork/attack the network.
Going to pull latest code and build on three nodes on different continents in an attempt to fork based on geo-separation.
Good news: I was unable to introduce a sustained fork by running four (4) clients in three (3) separate regions. Therefore I have returned to normal single delegate node for block production.
In Dry Run 9 I'd like to modify the test by increasing the number of delegates producing blocks from multiple nodes. The thought being that consecutive block production from a given series of nodes could produce a blockchain that differs from a separate set of nodes where peering does not support efficient transaction proposition. Given, the delegates producing from multiple nodes must do do consecutively which is by design random per round, so it would take a large set of multi-node delegates for even the possibility of the 'test' going to plan.
Is this a potential attack vector, malicious or otherwise?
Thoughts?
303
General Discussion / Re: Dry Run 8: Need for Speed
« on: July 13, 2014, 02:44:12 am »FOX is testing enabling the same delegate on two nodes to attempt to fork/attack the network.
Going to pull latest code and build on three nodes on different continents in an attempt to fork based on geo-separation.
304
General Discussion / Re: Dry Run 8: Need for Speed
« on: July 11, 2014, 09:43:36 pm »Can any delegate try to cheat and see what will happen.
My attempt at 'cheating' is to run the same delegate on two (2) nodes each with ~14 peer connections. My block production slot came and went without any apparent issue.
This somewhat surprises me, as I would expect both nodes to assume it is their time to create the block and independently publish a (potentially) different block to the network. Further, I assume the resulting differing blocks have the potential to create a fork.
Will this issue be raised only at higher transaction volumes when the block contain differing transactions and therefor different resulting hash?
This seems a bad practice for a delegate, as one should produce only a single block. How does the network react to this series of events and ultimately vote on this behavior?
305
General Discussion / Re: Dry Run 8: Need for Speed
« on: July 11, 2014, 06:44:12 pm »I need to know what a suggested port would be to allow traffic in on though
I am currently using TCP 8801 on my client. You may set it from the command line using the --p2p-port arg:
Code: [Select]
./bitshares_client --p2p-port 8801Do be sure to poke a hole in your firewall for TCP port 8801
Thanks,
Code: [Select]
wallet_approve_delegate fox
306
General Discussion / Re: Dry Run 8: Need for Speed
« on: July 10, 2014, 08:40:13 pm »
This code base seems much more stable than that of 12+ hours ago:
I currently have 15 connections:
Functioning delegate:
Code: [Select]
about
{
"bitshares_toolkit_revision": "2c46468de8e587229d54efe47d55fdf599c1da6f",
"bitshares_toolkit_revision_age": "6 hours ago",
"fc_revision": "87196008d4dacf292523e0b2e89e3af16e125dde",
"fc_revision_age": "25 hours ago",
"compile_date": "compiled on Jul 10 2014 at 13:18:03"
}
I currently have 15 connections:
Code: [Select]
network_add_node "114.215.104.153:47692" add
network_add_node "69.90.132.209:8801" add
network_add_node "23.99.109.40:8801" add
network_add_node "106.187.91.24:48254" add
network_add_node "188.138.107.159:8801" add
network_add_node "107.170.30.182:8801" add
network_add_node "92.243.18.20:8801" add
network_add_node "162.243.160.72:8801" add
network_add_node "207.12.89.119:39073" add
network_add_node "106.185.24.234:8801" add
network_add_node "128.199.180.112:8801" add
network_add_node "95.85.33.16:8764" add
network_add_node "107.170.170.214:8801" add
network_add_node "107.170.90.142:59285" add
network_add_node "106.187.91.24:8801" addFunctioning delegate:
Code: [Select]
wallet_approve_delegate fox
307
General Discussion / Re: Dry Run 8: Need for Speed
« on: July 10, 2014, 03:02:33 pm »
I'm only seeing two nodes 
:
What are you seeing?
:Code: [Select]
network_add_node "176.9.234.167:8801" add
network_add_node "92.243.18.20:8801" add
What are you seeing?
308
General Discussion / Re: Dry Run 8: Need for Speed
« on: July 09, 2014, 09:46:05 pm »
Anyone able to point me to some documentation to automate a start up script? I attempted the following with no luck:
What CLI args should be included within the input-log file? Those associated with ./bitshares_client or those within the running software?
My goal is to script the open and unlock of my wallet so my delegate produces following a reboot.
Thanks,
Code: [Select]
./bitshares_client --input-log "/home/myuser/myconfig.conf"What CLI args should be included within the input-log file? Those associated with ./bitshares_client or those within the running software?
My goal is to script the open and unlock of my wallet so my delegate produces following a reboot.
Thanks,
Code: [Select]
wallet_approve_delegate fox
310
General Discussion / Re: Dry Run 7: The Power of DPOS
« on: July 03, 2014, 09:03:37 pm »Quote
Those are all one guy and I know where he is sitting... init12+ is the seed node, init<12 is vikram.... I'll get on his case
Not intending to point a finger. Together we all make this a success.
Respectfully,
Fox
311
General Discussion / Re: Dry Run 7: The Power of DPOS
« on: July 03, 2014, 08:46:52 pm »
In the interest of increasing our delegate participation level closer to Bytemaster's goal of 90%, I suggest we vote out current delegates not producing blocks, thereby allowing in new delegates able to produce blocks consistently. It is my understanding the intended automated delegate voting functionality would down vote a delegate that misses a block(s).
There are two delegate names that stick out:
init* (4 delegates this round)
vikram* (13 delegates this round)
Please take a moment to remove them from your approved list:
There are two delegate names that stick out:
init* (4 delegates this round)
vikram* (13 delegates this round)
Please take a moment to remove them from your approved list:
Code: [Select]
wallet_approve_delegate init3 false
wallet_approve_delegate vikram false
312
General Discussion / Re: Dry Run 7: The Power of DPOS
« on: July 03, 2014, 06:15:34 pm »
I'm currently seeing the greatest number of peer connections ( 8 ) in 13 hours for my client. Here are the most resent peers that I have successfully connected to in the past two hours:
It may be helpful to increase the number of peer connections to your client:
Let's increase delegate participation. Please approve my actively block creating delegate:
Code: [Select]
network_add_node "107.170.172.14:46952" add
network_add_node "188.138.107.159:56497" add
network_add_node "146.185.186.245:8701" add
network_add_node "106.185.26.162:8761" add
network_add_node "107.170.30.182:8701" add
network_add_node "107.170.172.14:8701" add
network_add_node "162.243.219.145:8701" add
network_add_node "107.170.170.214:48387" add
network_add_node "95.85.33.16:8764" add
network_add_node "84.238.140.192:8701" add
network_add_node "176.9.234.166:8701" addIt may be helpful to increase the number of peer connections to your client:
Code: [Select]
network_set_advanced_node_parameters {"desired_number_of_connections":40 "maximum_number_of_connections":64}Let's increase delegate participation. Please approve my actively block creating delegate:
Code: [Select]
wallet_enable_delegate_block_production fox-delegate-98 true
314
General Discussion / Re: Dry Run 7: The Power of DPOS
« on: July 03, 2014, 02:38:59 pm »hope that help's
I added your list. However (unlikely as a result), now down to the following 3:
Code: [Select]
network_add_node "107.170.172.14:46952" add
network_add_node "188.138.107.159:56497" add
network_add_node "146.185.186.245:8701" add
315
General Discussion / Re: Dry Run 7: The Power of DPOS
« on: July 03, 2014, 02:22:02 pm »
I am looking for more peers. Currently I have only the following 4:
It is my understanding that 5 peers are required to produce a block. My slot is upcoming in less than 10 minutes. Anyone have some active peers I may add?
Thanks,
Fox
Code: [Select]
network_add_node "146.185.186.245:48628" add
network_add_node "107.170.30.182:8701" add
network_add_node "106.187.91.24:8701" add
network_add_node "188.138.107.159:56497" addIt is my understanding that 5 peers are required to produce a block. My slot is upcoming in less than 10 minutes. Anyone have some active peers I may add?
Thanks,
Fox
