Test Net for Advanced Users

[abit]

https://github.com/cryptonomex/graphene/releases

New Testnet is Here!

Please post your witness name so I can vote them in and add them to the growing list of active witnesses.

Running.

Code: [Select]

get_witness in.abit
{
  "id": "1.6.5247",
  "witness_account": "1.2.38993",
  "last_aslot": 0,
  "signing_key": "GPH65XNUxWdYGqGyW9NtXdRpNntumLYT1cJ7CNE7F78Pwxrnx6cbV",
  "vote_id": "1:5267",
  "total_votes": 0,
  "url": "https://github.com/abitmore",
  "total_missed": 0
}


Voted:   "next_maintenance_time": "44 minutes in the future" is when you will be active.

Thanks.
How to vote for multiple witnesses in cli_wallet?

//Update:
It seems that it's impossible to vote for multiple witnesses in cli_wallet https://github.com/cryptonomex/graphene/issues/323

[bytemaster]

https://github.com/cryptonomex/graphene/releases

New Testnet is Here!

Please post your witness name so I can vote them in and add them to the growing list of active witnesses.

Running.

Code: [Select]

get_witness in.abit
{
  "id": "1.6.5247",
  "witness_account": "1.2.38993",
  "last_aslot": 0,
  "signing_key": "GPH65XNUxWdYGqGyW9NtXdRpNntumLYT1cJ7CNE7F78Pwxrnx6cbV",
  "vote_id": "1:5267",
  "total_votes": 0,
  "url": "https://github.com/abitmore",
  "total_missed": 0
}


Voted:   "next_maintenance_time": "44 minutes in the future" is when you will be active.

[bytemaster]

@bytemaster
When are windows and Mac binaries of 0.9.3 available?

https://github.com/bitshares/bitshares/releases

[clayop]

@bytemaster
When are windows and Mac binaries of 0.9.3 available?

[abit]

https://github.com/cryptonomex/graphene/releases

New Testnet is Here!

Please post your witness name so I can vote them in and add them to the growing list of active witnesses.

Running.

Code: [Select]

get_witness in.abit
{
  "id": "1.6.5247",
  "witness_account": "1.2.38993",
  "last_aslot": 0,
  "signing_key": "GPH65XNUxWdYGqGyW9NtXdRpNntumLYT1cJ7CNE7F78Pwxrnx6cbV",
  "vote_id": "1:5267",
  "total_votes": 0,
  "url": "https://github.com/abitmore",
  "total_missed": 0
}


[abit]

Testers that want to flood the network, do not use your witness node as the RPC server. 

Also please take note of the new logging to the console that includes latencies of blocks received.    Those on a DigitalOcean machine in NYC3 should have around 0 MS latency for many blocks    

Also... to get your witness voted in you will have to vote for all 11 init witnesses PLUS your own witness.

Building..

[bytemaster]

Testers that want to flood the network, do not use your witness node as the RPC server. 

Also please take note of the new logging to the console that includes latencies of blocks received.    Those on a DigitalOcean machine in NYC3 should have around 0 MS latency for many blocks    

Also... to get your witness voted in you will have to vote for all 11 init witnesses PLUS your own witness. 

[CLains]

We rollin'

[bytemaster]

https://github.com/cryptonomex/graphene/releases

New Testnet is Here!

Please post your witness name so I can vote them in and add them to the growing list of active witnesses. 

[puppies]

I see the recent commit, but do not see a new tag or release. Is there a new testnet up using master?  What is the seed node(s) and where is the genesis.json file located?

I think there is no new test net right now. The last one is dead, so we need to wait for the new one.

Yeah.  I know I'm anxious for a new testnet.  Nothing we can do but wait.

[abit]

I see the recent commit, but do not see a new tag or release. Is there a new testnet up using master?  What is the seed node(s) and where is the genesis.json file located?

I think there is no new test net right now. The last one is dead, so we need to wait for the new one.

[Riverhead]

I did a checkout of Master and got a pile of new stuff. Nothing in the submodules though.

Code: [Select]

Updating 81cc8e4..f0502ee
Fast-forward
 libraries/app/database_api.cpp                                 |   1 +
 libraries/app/impacted.cpp                                     |  11 +++++++-
 libraries/chain/db_block.cpp                                   | 174 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++-------------------------------------------------------
 libraries/chain/db_maint.cpp                                   |  21 +++------------
 libraries/chain/db_management.cpp                              |  44 +++++++++---------------------
 libraries/chain/db_market.cpp                                  |  11 ++++++--
 libraries/chain/db_update.cpp                                  |   6 -----
 libraries/chain/fork_database.cpp                              |   2 ++
 libraries/chain/include/graphene/chain/database.hpp            |  10 ++++---
 libraries/chain/include/graphene/chain/db_with.hpp             |  30 ++++++++++++++++-----
 libraries/chain/include/graphene/chain/exceptions.hpp          |   2 ++
 libraries/chain/include/graphene/chain/protocol/asset_ops.hpp  |  25 +++++++++++++++++
 libraries/chain/include/graphene/chain/protocol/operations.hpp |   6 +++--
 libraries/chain/proposal_evaluator.cpp                         |   2 +-
 libraries/chain/vesting_balance_evaluator.cpp                  |   2 +-
 tests/common/database_fixture.cpp                              |  14 +++++++---
 tests/tests/authority_tests.cpp                                |  32 ++++++++++++----------
 tests/tests/block_tests.cpp                                    |   8 +++---
 18 files changed, 231 insertions(+), 170 deletions(-)
james@james-desktop:~/github/graphene$ git submodule update --init --recursive
james@james-desktop:~/github/graphene$


[Fox]

I see the recent commit, but do not see a new tag or release. Is there a new testnet up using master?  What is the seed node(s) and where is the genesis.json file located?

[bytemaster]

We just pushed a significant set of updates designed to fix issues discovered during the prior test net.

1. Transactions from an orphaned block now get migrated (if possible) to the main chain to be included.   This should fix a lot of missing transaction issues.
2.  We fixed an issue where nodes could get in an inconsistent state.
3. We added unit tests to check for these conditions.

Perhaps the most significant change to the meaning of transactions is that they no longer reference the "new block's timestamp" and instead only reference chainstate from the
prior head block or the application of prior transactions in the current block.   This decision was made to ensure that all state referenced by a transaction that exists at the
time the transaction was first received still exists at the time the block is eventually produced.   This means that for the purposes of expiration all transactions occur as if
the time was the head block time and not as if the time was the time the block that included them was created.  Implication:   If you have a transaction that expires at 1:23:01 and
the head block time is 1:23:00 and the next block produced is 1:30:00 then the block at 1:30:00 can include the transaction that expired at 1:23:01.

Considering our goal of 1 second blocks and 99.9% participation this particular issue should not make any significant difference.

[xeroc]

Testnet has stopped .. next one is close