Author [EN] [ZH] [ES] [PT] [IT] [DE] [FR] [NL] [TR] [SR] [AR] [RU] [EN] [ZH] [ES] [PT] [IT] [DE] [FR] [NL] [TR] [SR] [AR] [RU] [EN] [ZH] [ES] [PT] [IT] [DE] [FR] [NL] [TR] [SR] [AR] [RU] Topic: Dry Run 2: The Real Deal  (Read 19293 times)

0 Members and 1 Guest are viewing this topic.

Offline toast

Dry Run 2: The Real Deal
« on: June 12, 2014, 11:24:02 PM »

We'll use this chain for voting for initial delegates for the real launch (assuming nothing goes wrong). Keep your shares if you want to have a say in who the initial delegates are.

Of course we cannot expect delegate campaigns to start or the masses to start voting until our GUI is ready. We'll start a separate thread for that, with pretty pictures. Soon.

Initial delegates, do this: https://github.com/BitShares/bitshares_toolkit/wiki/DPOS-initial-delegate-setup

Note that we removed some delegates for this round due to inactivity (or rather, inactivity as seen on our fork).
You can check if yours were the ones we removed here:
https://raw.githubusercontent.com/BitShares/bitshares_toolkit/master/libraries/blockchain/genesis.json


Notes
* All delegates were registered with "init-delegate-N" as names, this is expected. These are pre-registered accounts and you do not need to make new
* for people trying to get this to work on debian and getting import errors for keys, make sure that you compile with gcc 4.8, as gcc 4.7 doesn't work (compiles correctly but then crashes randomly or fails importing keys in weird places...)
« Last Edit: June 13, 2014, 02:06:50 AM by toast »
Do not use this post as information for making any important decisions. The only agreements I ever make are informal and non-binding. Take the same precautions as when dealing with a compromised account, scammer, sockpuppet, etc.

Offline crazybit

  • Sr. Member
  • ****
  • Posts: 415
    • View Profile
Re: Dry Run 2: The Real Deal
« Reply #1 on: June 12, 2014, 11:30:28 PM »
does it mean the the top 100 active delegates in this test chain will be selected as the initial delegates for the real launch? can i apply the initial delegates in this test chain?if yes, how many initial delegates can i apply??

if it is not too late to apply the initial delegates in this test chain, please help to include the following delegates. thanks

public key: XTS7H28tfWkAcJDvxW7wJBPRdM4UHbmdcP3JP8vFv1cQP7KNtaq2Z
public key: XTS5g1QvMhU88HdZcySwqQRg4fqsGwNZ9nLSZFpBofp6XVfyyNP8n
public key: XTS8dhZN4jLXmTDivEXWLB227KhzJpuvVX7M8y6AQPovw7bVTBR7m
public key: XTS5p6iXruAGpneXPt252xWk8STpBNvqkwwNw7uaWYFRQ1ankgTMV
public key: XTS5KKdtjAXAjFbQbB4bwPiyPShp1o47QWRPVKqaxvffnhTZfq9cF
« Last Edit: June 13, 2014, 12:05:16 AM by CrazyBit »

Offline liondani

Re: Dry Run 2: The Real Deal
« Reply #2 on: June 12, 2014, 11:31:46 PM »
when somebody try now to get a delegate is it to late?
  https://bitshares.OPENLEDGER.info/?r=GREECE  | You are in Control | BUY | SELL | SHORT | SWAP | LOAN | TRADE |  

Offline bytemaster

Re: Dry Run 2: The Real Deal
« Reply #3 on: June 12, 2014, 11:54:23 PM »
when somebody try now to get a delegate is it to late?

Nothing is every too late... if you work hard and help in the testing then you will likely be selected and voted in.       

For the latest updates checkout my blog: http://bytemaster.bitshares.org
Anything said on these forums does not constitute an intent to create a legal obligation or contract between myself and anyone else.   These are merely my opinions and I reserve the right to change them at any time.

Offline sfinder

  • Hero Member
  • *****
  • Posts: 1205
  • 4 Cores CPU+100GB SSD+anti-DDoS Pro
    • View Profile
Re: Dry Run 2: The Real Deal
« Reply #4 on: June 13, 2014, 12:25:03 AM »



Quote
getinfo
{
  "blockchain_head_block_num": 8,
  "blockchain_head_block_time": "20140613T001830",
  "blockchain_confirmation_requirement": 291,
  "blockchain_average_delegate_participation": 3.053435114503817,
  "network_num_connections": 1,
  "wallet_unlocked_seconds_remaining": 0,
  "wallet_next_block_production_time": "20140613T002415",
  "wallet_seconds_until_next_block_production": 25,
  "wallet_local_time": "20140613T002350",
  "blockchain_random_seed": "23eeea969c96c5f75eb865bc42852939f6014923",
  "blockchain_shares": 9999999984584,
  "network_num_connections_max": 12,
  "network_protocol_version": 101,
  "wallet_open": true,
  "wallet_unlocked_until": "",
  "wallet_version": 100
}
微博:星在飘我在找|BTS X 受托人delegate ID:baidu
中国教育书店合作将20%收入捐献给贫困山区学生。
Cooperating with China Education Bookstore and will donate 20% of delegate income to the poor students

Offline alt

Re: Dry Run 2: The Real Deal
« Reply #5 on: June 13, 2014, 12:40:39 AM »
Can I import my delegate key in 2 nodes this time?

Offline bytemaster

Re: Dry Run 2: The Real Deal
« Reply #6 on: June 13, 2014, 01:07:02 AM »
As long as only one is unlocked at a time. 


Sent from my iPhone using Tapatalk
For the latest updates checkout my blog: http://bytemaster.bitshares.org
Anything said on these forums does not constitute an intent to create a legal obligation or contract between myself and anyone else.   These are merely my opinions and I reserve the right to change them at any time.

Offline muse-umum

  • Hero Member
  • *****
  • Posts: 717
  • BitShares everything
    • View Profile
Re: Dry Run 2: The Real Deal
« Reply #7 on: June 13, 2014, 01:13:15 AM »
As long as only one is unlocked at a time. 


Sent from my iPhone using Tapatalk

What if both 2 nodes are unlocked ? Get fired ?

Offline bytemaster

Re: Dry Run 2: The Real Deal
« Reply #8 on: June 13, 2014, 01:13:54 AM »
Try it.  I dare you.


Sent from my iPhone using Tapatalk
For the latest updates checkout my blog: http://bytemaster.bitshares.org
Anything said on these forums does not constitute an intent to create a legal obligation or contract between myself and anyone else.   These are merely my opinions and I reserve the right to change them at any time.

Offline puppies

Re: Dry Run 2: The Real Deal
« Reply #9 on: June 13, 2014, 01:27:18 AM »
I've got my delegates up and creating blocks.  I also have a seed node running on 95.85.33.16:8764.  On a side note, has anyone managed to get the Qt wallet to work outside of OSX?
https://metaexchange.info | Bitcoin<->Altcoin exchange | Instant | Safe | Low spreads

Offline toast

Re: Dry Run 2: The Real Deal
« Reply #10 on: June 13, 2014, 01:54:16 AM »
As long as only one is unlocked at a time. 


Sent from my iPhone using Tapatalk

What if both 2 nodes are unlocked ? Get fired ?

Not automatically. You should try it, see if you can cause a fork.

Even better, get two of your clients connected to each other and not to the rest of the network, then reconnect once you have your own chain.
Do not use this post as information for making any important decisions. The only agreements I ever make are informal and non-binding. Take the same precautions as when dealing with a compromised account, scammer, sockpuppet, etc.

Offline bitcoinerS

  • Hero Member
  • *****
  • Posts: 584
    • View Profile
Re: Dry Run 2: The Real Deal
« Reply #11 on: June 13, 2014, 02:02:26 AM »
Just pulled latest code and rebuilt delegate node. Deleted .Bitshares/ dir and recreated wallet. Tried to re-import delegate private keys, but now I get this error on every delegate key:

Code: [Select]
wallet_import_private_key <mykey>
10 assert_exception: Assert Exception
registered_account: the key must belong to a registered account or an account name must be specified
    {}
    th_a  wallet.cpp:931 import_private_key

    {"account_name":""}
    th_a  wallet.cpp:970 import_private_key

    {"account_name":""}
    th_a  wallet.cpp:989 import_wif_private_key

    {}
    th_a  common_api_client.cpp:252 wallet_import_private_key


and it seems I am on new blockchain

Code: [Select]
get_info
{
  "blockchain_head_block_num": 74,
  "blockchain_head_block_time": "20140613T015945",

my delegates were
init-delegate-38 through 41
>>> approve bitcoiners

Offline toast

Re: Dry Run 2: The Real Deal
« Reply #12 on: June 13, 2014, 02:06:12 AM »
Just pulled latest code and rebuilt delegate node. Deleted .Bitshares/ dir and recreated wallet. Tried to re-import delegate private keys, but now I get this error on every delegate key:

Code: [Select]
wallet_import_private_key <mykey>
10 assert_exception: Assert Exception
registered_account: the key must belong to a registered account or an account name must be specified
    {}
    th_a  wallet.cpp:931 import_private_key

    {"account_name":""}
    th_a  wallet.cpp:970 import_private_key

    {"account_name":""}
    th_a  wallet.cpp:989 import_wif_private_key

    {}
    th_a  common_api_client.cpp:252 wallet_import_private_key


and it seems I am on new blockchain

Code: [Select]
get_info
{
  "blockchain_head_block_num": 74,
  "blockchain_head_block_time": "20140613T015945",

my delegates were
init-delegate-38 through 41

You can check if yours were the ones we removed here:
https://raw.githubusercontent.com/BitShares/bitshares_toolkit/master/libraries/blockchain/genesis.json

Were you inactive during the last test? I only removed delegates with 0 blocks produced according to my client.
Do not use this post as information for making any important decisions. The only agreements I ever make are informal and non-binding. Take the same precautions as when dealing with a compromised account, scammer, sockpuppet, etc.

Offline muse-umum

  • Hero Member
  • *****
  • Posts: 717
  • BitShares everything
    • View Profile
Re: Dry Run 2: The Real Deal
« Reply #13 on: June 13, 2014, 02:21:45 AM »
As long as only one is unlocked at a time. 


Sent from my iPhone using Tapatalk

What if both 2 nodes are unlocked ? Get fired ?

Not automatically. You should try it, see if you can cause a fork.

Even better, get two of your clients connected to each other and not to the rest of the network, then reconnect once you have your own chain.

Installing another Ubuntu now to try.

Offline bitcoinerS

  • Hero Member
  • *****
  • Posts: 584
    • View Profile
Re: Dry Run 2: The Real Deal
« Reply #14 on: June 13, 2014, 02:35:41 AM »
Just pulled latest code and rebuilt delegate node. Deleted .Bitshares/ dir and recreated wallet. Tried to re-import delegate private keys, but now I get this error on every delegate key:

Code: [Select]
wallet_import_private_key <mykey>
10 assert_exception: Assert Exception
registered_account: the key must belong to a registered account or an account name must be specified
    {}
    th_a  wallet.cpp:931 import_private_key

    {"account_name":""}
    th_a  wallet.cpp:970 import_private_key

    {"account_name":""}
    th_a  wallet.cpp:989 import_wif_private_key

    {}
    th_a  common_api_client.cpp:252 wallet_import_private_key


and it seems I am on new blockchain

Code: [Select]
get_info
{
  "blockchain_head_block_num": 74,
  "blockchain_head_block_time": "20140613T015945",

my delegates were
init-delegate-38 through 41

You can check if yours were the ones we removed here:
https://raw.githubusercontent.com/BitShares/bitshares_toolkit/master/libraries/blockchain/genesis.json

Were you inactive during the last test? I only removed delegates with 0 blocks produced according to my client.

I was active and it seems that list genesis.json includes my delegate names but keys changed..
There were many forks in the chain, my delegate node must have been tracking a different one from yours.

Code: [Select]
{
         "name": "init-delegate-38",
         "is_delegate": true,
         "owner": "XTS7Fbh67uWB1vfvxpqLMYrxJVpy1eqW1S9sgGTFs5GRF3tKsusuz"
       },{
         "name": "init-delegate-39",
         "is_delegate": true,
         "owner": "XTS7DEUd9uPyY8TVZ9BxJbTTkV5qK9a49sFDL7Y5DHbehUc89bPzX"
       },{
         "name": "init-delegate-40",
         "is_delegate": true,
         "owner": "XTS8XD2PcH9BoiLT1gtLrnUcSAob41YDr1enLp3oaWoqzUj5xNsUS"
       },{
         "name": "init-delegate-41",
         "is_delegate": true,
         "owner": "XTS73tZqCAgRxNTeBCt2CMSvoMZQLQFodvrJWLvAebVVNYee6TVJs"
       },{


Here are my keys that were active yesterday.

XTS6ezsAe72hVoMq4mC4fnAAF2XYqprcpt4vZ5nkqUoZn8xsSWB5Z
XTS72Xc5wBYmWQrAqcPoU6RSEegB3CosNh82wbf4QkKquJtbhgPWL
XTS7DeMWhGV8P7oiKoigtGqFKDfauB83Nrxy5FpMwLEjMw7wC8UVe
XTS73iK3RkkijdfgzH5mioB4wzWFNsmsvwtsNPnkoHAApHK6cbMz3


How do I get them working again?
« Last Edit: June 13, 2014, 02:37:39 AM by bitcoinerS »
>>> approve bitcoiners

 

Google+