Test Net for Advanced Users

[puppies]

Reminder that
apt-add-repository ppa:showard314/ppa
has graphene Ubuntu packages built daily off of master in case you're a lurker that wants to jump in and give it a shot

can u write a little tut on how to start a witness?

i'm stuck when i try tu run ./witness_node with the latest json...no idea what i have to do 

from where you would like to run the witness node try

Code: [Select]

wget https://github.com/cryptonomex/graphene/releases/download/test2b/aug-31-testnet-genesis.json
mkdir test
nano test/config.ini
Then copy the code below into the terminal window and hit control-x and then y and then enter.

Code: [Select]

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

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

# Pairs of [BLOCK_NUM,BLOCK_ID] that should be enforced as checkpoints.
# checkpoint =

# Endpoint for websocket RPC to listen on
rpc-endpoint = 127.0.0.1:8090

# Endpoint for TLS websocket RPC to listen on
# rpc-tls-endpoint =

# The TLS certificate file for this server
# server-pem =

# Password for this certificate
# server-pem-password =

# File to read Genesis State from
genesis-json = aug-31-testnet-genesis.json

# JSON file specifying API permissions
# api-access =

# Enable block production, even if the chain is stale.
enable-stale-production = false

# Percent of witnesses (0-99) that must be participating in order to produce blocks
required-participation = false

# Allow block production, even if the last block was produced by the same witness.
allow-consecutive = false

# ID of witness controlled by this node (e.g. "1.6.5", quotes are required, may specify multiple times)
# witness-id =

# Tuple of [PublicKey, WIF private key] (may specify multiple times)
private-key = ["GPH6MRyAjQq8ud7hVNYcfnVPJqcVpscN5So8BhtHuGYqET5GDW5CV","5KQwrPbwdL6PhXujxW37FSSQZ1JiwsST4cqQzDeyXtP79zkvFD3"]

# Account ID to track history for (may specify multiple times)
# track-account =

# Track market history by grouping orders into buckets of equal size measured in seconds specified as a JSON array of numbers
bucket-size = [15,60,300,3600,86400]

# How far back in time to track history for each bucket size, measured in the number of buckets (default: 1000)
history-per-size = 1000

# declare an appender named "stderr" that writes messages to the console
[log.console_appender.stderr]
stream=std_error

# declare an appender named "p2p" that writes messages to p2p.log
[log.file_appender.p2p]
filename=logs/p2p/p2p.log
# filename can be absolute or relative to this config file

# route any messages logged to the default logger to the "stderr" logger we
# declared above, if they are info level are higher
[logger.default]
level=info
appenders=stderr

# route messages sent to the "p2p" logger to the p2p appender declared above
[logger.p2p]
level=debug
appenders=p2p
after that type

Code: [Select]

witness_node -d testadd a ./ to the beginning of that if you have built the source code yourself and haven't used maqs ppa.  Although if thats the case you will need to be running this is the same directory as your witness_node binary.

Let me know if this doesn't make sense, or you have any other questions.  Once you have the witness node running you will be able to run the cli_wallet and set up a witness.  I can help you with that if needed. 


edit had wrong json download in there.  Sorry

[puppies]

would there be any benefit spamming from multiple accounts? I have some time tonight and could join the party, I just don't have any core. I have my delegate on a vps and would be spamming from my home computer. Also puppies, are you using the flood network command or the script you wrote?

I am spamming with a keyboard emulator called autokey.  It allows you to set up phrases as hotkeys, I set <up><enter> a whole bunch of times, and set it to a hot key.  I set up the wallet transfer once to make sure it is okay, and then spam the hotkey.  Every time you hit the key it will queue up another iteration of the phrase.  I spam it for 30 seconds or so, and it will go for hours.

I am sure there is a much more elegant way to handle this, but I didn't want to take the time to figure it out.  I knew this would work, and would be easy to set up.

[spartako]

I have also created a script in nodejs (that I will publish tomorrow on github) with the list of last 101 blocks with delegate names to see who is producing blocks:

Code: [Select]

48340 '1.6.70' 'init69'
48339 '1.6.18' 'init17'
48338 '1.6.4232' 'spartako'
48337 '1.6.3968' 'riverhead'
48336 '1.6.64' 'init63'
48335 '1.6.7' 'init6'
48334 '1.6.75' 'init74'
48333 '1.6.46' 'init45'
48332 '1.6.5248' 'betaxtrade'
48331 '1.6.45' 'init44'
48330 '1.6.50' 'init49'
48329 '1.6.49' 'init48'
48328 '1.6.31' 'init30'
48327 '1.6.40' 'init39'
48326 '1.6.2' 'init1'
48325 '1.6.62' 'init61'
48324 '1.6.3' 'init2'
48323 '1.6.27' 'init26'
48322 '1.6.28' 'init27'
48321 '1.6.21' 'init20'
48320 '1.6.92' 'init91'
48319 '1.6.23' 'init22'
48318 '1.6.47' 'init46'
48317 '1.6.1538' 'delegate-clayop'
48316 '1.6.37' 'init36'
48315 '1.6.55' 'init54'
48314 '1.6.84' 'init83'
48313 '1.6.74' 'init73'
48312 '1.6.68' 'init67'
48311 '1.6.22' 'init21'
48310 '1.6.78' 'init77'
48309 '1.6.83' 'init82'
48308 '1.6.42' 'init41'
48307 '1.6.38' 'init37'
48306 '1.6.53' 'init52'
48305 '1.6.81' 'init80'
48304 '1.6.11' 'init10'
48303 '1.6.89' 'init88'
48302 '1.6.69' 'init68'
48301 '1.6.56' 'init55'
48300 '1.6.35' 'init34'
48299 '1.6.82' 'init81'
48298 '1.6.5247' 'in.abit'
48297 '1.6.72' 'init71'
48296 '1.6.39' 'init38'
48295 '1.6.36' 'init35'
48294 '1.6.16' 'init15'
48293 '1.6.29' 'init28'
48292 '1.6.67' 'init66'
48291 '1.6.12' 'init11'
48290 '1.6.41' 'init40'
48289 '1.6.34' 'init33'
48288 '1.6.8' 'init7'
48287 '1.6.66' 'init65'
48286 '1.6.4' 'init3'
48285 '1.6.70' 'init69'
48284 '1.6.64' 'init63'
48283 '1.6.90' 'init89'
48282 '1.6.17' 'init16'
48281 '1.6.14' 'init13'
48280 '1.6.20' 'init19'
48279 '1.6.32' 'init31'
48278 '1.6.10' 'init9'
48277 '1.6.79' 'init78'
48276 '1.6.45' 'init44'
48275 '1.6.80' 'init79'
48274 '1.6.1531' 'delegate-1.lafona'
48273 '1.6.26' 'init25'
48272 '1.6.54' 'init53'
48271 '1.6.18' 'init17'
48270 '1.6.9' 'init8'
48269 '1.6.85' 'init84'
48268 '1.6.61' 'init60'
48267 '1.6.7' 'init6'
48266 '1.6.60' 'init59'
48265 '1.6.86' 'init85'
48264 '1.6.46' 'init45'
48263 '1.6.25' 'init24'
48262 '1.6.33' 'init32'
48261 '1.6.58' 'init57'
48260 '1.6.5248' 'betaxtrade'
48259 '1.6.43' 'init42'
48258 '1.6.59' 'init58'
48257 '1.6.1' 'init0'
48256 '1.6.19' 'init18'
48255 '1.6.48' 'init47'
48254 '1.6.91' 'init90'
48253 '1.6.44' 'init43'
48252 '1.6.73' 'init72'
48251 '1.6.65' 'init64'
48250 '1.6.87' 'init86'
48249 '1.6.88' 'init87'
48248 '1.6.24' 'init23'
48247 '1.6.6' 'init5'
48246 '1.6.30' 'init29'
48245 '1.6.52' 'init51'
48244 '1.6.51' 'init50'
48243 '1.6.4232' 'spartako'
48242 '1.6.57' 'init56'
48241 '1.6.76' 'init75'
48240 '1.6.1527' 'dele-puppy'


[lafona]

would there be any benefit spamming from multiple accounts? I have some time tonight and could join the party, I just don't have any core. I have my delegate on a vps and would be spamming from my home computer. Also puppies, are you using the flood network command or the script you wrote?

[spartako]

I'm producing blocks:

Code: [Select]

get_object 1.13.171
[{
    "id": "1.13.171",
    "owner": "1.2.72728",
    "balance": {
      "amount": 165000000,
      "asset_id": "1.3.0"
    },
    "policy": [
      1,{
        "vesting_seconds": 86400,
        "start_claim": "1970-01-01T00:00:00",
        "coin_seconds_earned": "9032250000000",
        "coin_seconds_earned_last_update": "2015-09-03T22:04:05"
      }
    ]
  }
]



[puppies]

Thanks.  Spamming away.

[bytemaster]

I just need more CORE to keep spamming

Code: [Select]

"lifetime_fees_paid": "38644604445",


Which account should I send you core on?

puppies please

500K core has been sent your way.

[puppies]

I just need more CORE to keep spamming

Code: [Select]

"lifetime_fees_paid": "38644604445",


Which account should I send you core on?

puppies please

[bytemaster]

I just need more CORE to keep spamming

Code: [Select]

"lifetime_fees_paid": "38644604445",


Which account should I send you core on?

[puppies]

I just need more CORE to keep spamming

Code: [Select]

"lifetime_fees_paid": "38644604445",


[JA]

Reminder that
apt-add-repository ppa:showard314/ppa
has graphene Ubuntu packages built daily off of master in case you're a lurker that wants to jump in and give it a shot

can u write a little tut on how to start a witness?

i'm stuck when i try tu run ./witness_node with the latest json...no idea what i have to do 

[bytemaster]

So far there have been 54,838 operations published on the test network and I can reindex the blockchain in 50 seconds  (greater than 1000 operations per second) completely ignoring the fact that the test network has 100x as many maintenance blocks as it should.

In my profiling I see that 92% of the reindexing time is un perform_chain_maintenance which means that we are currently processing ~15K operations per second on average. 

Given that the vast majority of blocks are empty the time spent doing empty block processing is lowering the average TPS  my a significant margin.

Great work for everyone who has helped publish over 50K transactions on this test network so far

[clayop]

I'm producing blocks

Code: [Select]

get_object 1.13.162
[{
    "id": "1.13.162",
    "owner": "1.2.22310",
    "balance": {
      "amount": 174000000,
      "asset_id": "1.3.0"
    },
    "policy": [
      1,{
        "vesting_seconds": 86400,
        "start_claim": "1970-01-01T00:00:00",
        "coin_seconds_earned": "13755490000000",
        "coin_seconds_earned_last_update": "2015-09-03T21:19:15"
      }
    ]
  }
]

[abit]

I did find a good way of ensuring that your witness is producing blocks.

If you get_witness <witness_name>

Code: [Select]

unlocked >>> get_witness dele-puppy
get_witness dele-puppy
{
  "id": "1.6.1527",
  "witness_account": "1.2.22294",
  "last_aslot": 49430,
  "signing_key": "GPH75xxKG4ZeztPpnhmFch99smunUWMvDy9mB6Le497vpAA3XUXaD",
  "pay_vb": "1.13.163",
  "vote_id": "1:1526",
  "total_votes": "29174714611",
  "url": ""
}
unlocked >>>
It will give you your vesting pay object as "pay_vb"  from there you can get_object 1.13.163

Code: [Select]

unlocked >>> get_object 1.13.163
get_object 1.13.163
[{
    "id": "1.13.163",
    "owner": "1.2.22294",
    "balance": {
      "amount": 326000000,
      "asset_id": "1.3.0"
    },
    "policy": [
      1,{
        "vesting_seconds": 86400,
        "start_claim": "1970-01-01T00:00:00",
        "coin_seconds_earned": "28080000000000",
        "coin_seconds_earned_last_update": "2015-09-03T20:56:30"
      }
    ]
  }
]
unlocked >>>

Every time you generate a block the "amount": goes up by 1000000.  So you can see that dele-puppy has generated 326 blocks.  Not quite real time, but easier than watching the witness_node screen, or stats.bitshares.eu for your number.

Interesting. 
I do find my block-producing witness is much more stable than last testnet. But my seed node got out of sync now and then.

Code: [Select]

get_object 1.13.160
[{
    "id": "1.13.160",
    "owner": "1.2.38899",
    "balance": {
      "amount": 379000000,
      "asset_id": "1.3.0"
    },
    "policy": [
      1,{
        "vesting_seconds": 86400,
        "start_claim": "1970-01-01T00:00:00",
        "coin_seconds_earned": "32659200000000",
        "coin_seconds_earned_last_update": "2015-09-03T21:09:00"
      }
    ]
  }
]


[puppies]

"transaction_merkle_root": "00https://bitsharestalk.org/Themes/default/images/bbc/left.gif00000000000000000000000000000000000000",

What is up with this line?

lol.  copy paste error.

I did find a good way of ensuring that your witness is producing blocks.

If you get_witness <witness_name>

Code: [Select]

unlocked >>> get_witness dele-puppy
get_witness dele-puppy
{
  "id": "1.6.1527",
  "witness_account": "1.2.22294",
  "last_aslot": 49430,
  "signing_key": "GPH75xxKG4ZeztPpnhmFch99smunUWMvDy9mB6Le497vpAA3XUXaD",
  "pay_vb": "1.13.163",
  "vote_id": "1:1526",
  "total_votes": "29174714611",
  "url": ""
}
unlocked >>>
It will give you your vesting pay object as "pay_vb"  from there you can get_object 1.13.163

Code: [Select]

unlocked >>> get_object 1.13.163
get_object 1.13.163
[{
    "id": "1.13.163",
    "owner": "1.2.22294",
    "balance": {
      "amount": 326000000,
      "asset_id": "1.3.0"
    },
    "policy": [
      1,{
        "vesting_seconds": 86400,
        "start_claim": "1970-01-01T00:00:00",
        "coin_seconds_earned": "28080000000000",
        "coin_seconds_earned_last_update": "2015-09-03T20:56:30"
      }
    ]
  }
]
unlocked >>>

Every time you generate a block the "amount": goes up by 1000000.  So you can see that dele-puppy has generated 326 blocks.  Not quite real time, but easier than watching the witness_node screen, or stats.bitshares.eu for your number.