BitShares Forum

Main => General Discussion => Topic started by: toast on June 07, 2014, 06:56:49 pm

Title: Initial delegates, let's get ready!
Post by: toast on June 07, 2014, 06:56:49 pm
You *must* participate in the next test network to be an initial delegate. This will be a complete dry run with the correct genesis block.

We will pick delegates as soon as enough qualified people have followed these steps - don't put this off!

Ok guys stop saying "reserved" because this gives us no indication of if or when you will actually do it. This isn't the "candidate billboard" thread.


Please do these steps:

1) Make sure you are able to install and run the command-line client. You will find instructions in the github repo:
https://github.com/nmushegian/bitshares_toolkit/blob/master/BUILD_UBUNTU.md
https://github.com/nmushegian/bitshares_toolkit/blob/master/BUILD_OSX.md
https://github.com/nmushegian/bitshares_toolkit/blob/master/BUILD_WIN32.md

2) Set up your dedicated node. Tell us:
* Your IP and port ONLY IF you want to be a seed node (good chance to flex your delegate muscles if you can withstand DDOS)
* Your node's specs
* Your node's geographic location

3) Generate up to five keys. Use the utility at bitshares_toolkit/programs/utils/bts_create_key

Share with us the *public key* (not address)
Keep the *private key WIF format* (not the plain private key - actually keep both, WIF is just what you import)

For example:

toast-delegate-1 :  XTS76f6d9qrsvYJjv3ycbWWihaZyYBNCjCmLDoKHrPTooJKCQKBtD
toast-delegate-2 :  XTS6Sq54D8dNXRWeR9TLtMX4VqKDqfrQXBpC5dUkKA2ayrmUZVi2u


(and keep (do not share!) the ones that look like: 5HvMYtvvqrfBbP7GkFHHPPFCW4RfEftknj9mqHCvipEcgfecK8E )


We will choose a diverse set of initial nodes for this test network. The real test network will use whichever delegates are active at the end of this test. This means if your node goes offline during testing, you could get voted out and lose your spot! Likewise, if you are late to the party but convince people to vote you in, you could be an initial delegate.

Once again, being an initial delegate doesn't mean much because you still have to stay voted in.

To load your delegate key into the wallet do this:
Code: [Select]
wallet_add_contact_account your-delegate-1 XTS6VeDfUq4kT37yzWJs5stJEM3F11i1v6xghQBZYrFENp4aE843y
wallet_import_private_key ${PRIVATE_KEY FOR XTS6VeDfUq4kT37yzWJs5stJEM3F11i1v6xghQBZYrFENp4aE843y}
Title: Re: Initial delegates, let's get ready!
Post by: Ggozzo on June 07, 2014, 08:40:22 pm
Nice! When are you going to start? Tomorrow? Monday?
Title: Re: Initial delegates, let's get ready!
Post by: bytemaster on June 07, 2014, 08:44:44 pm
Nice! When are you going to start? Tomorrow? Monday?

Once we have prepared as much documentation and validation as possible. 
Title: Re: Initial delegates, let's get ready!
Post by: AdamBLevine on June 07, 2014, 08:59:41 pm
Enjoy!  Looks too fiddly for a user like me, I just need an application I can install, configure and run.
Title: Re: Initial delegates, let's get ready!
Post by: emski on June 07, 2014, 11:25:26 pm
These are the public keys generated from bts_create_key

XTS6TMMu8B5MBEgj2kg9pGF8dzrWBtj5CpKHHQxM3x4EsvD4mJMUK
XTS7diW1nWPWrxkwuqXkwmxFN4qrQ7jyVNcRhqGqrriVvK2udynhD
XTS7bUdQ41J4vhNVBkmbqDKGiftrmQNrL1vCx881Fg4R2hE5r6P2Z
XTS6XtS7F5Fy3dUVSUKHJHN1dC66VaruRFkKmo8um6QB24Xsf2mzF
XTS8ZhbpwEgwgV1gjCNrYfMDxsB6diofNtsg1m4yN62Zii1EwpK7B

Node address is (emski edit: IP can be resolved from address, so its removed) (IP: toast edit: I removed your IP because I'm dumb and shouldn't have asked for it).
Name: Mavenfrog
Location: Sofia, Bulgaria

Hardware:
i7 3770
32 GB ddr3 1600mhz ram
240GB SSD
4x1 TB HDD in HW RAID

Software:
Running VMWare ESXi 5.5.0 Hypervisor
Guest VM - 4 virtual CPU cores and 8 GB of ram reserved for the node (can increase this if required)
OS Ubuntu server 14.04

* backup internet connection, UPS

GL & HF to everyone
Title: Re: Initial delegates, let's get ready!
Post by: emski on June 07, 2014, 11:32:26 pm
Are you going to specify branch/tag/revision to use ?
Are you going to specify timeframe ?
Title: Re: Initial delegates, let's get ready!
Post by: tonyk on June 07, 2014, 11:36:37 pm

GL & HF to everyone

Успех и късмет!!!
Title: Re: Initial delegates, let's get ready!
Post by: sfinder on June 08, 2014, 12:14:40 am
pan2pan-01:  XTS6tmvXdn2vJss4a4ADVUUi8GbAC37H6HJRcVeFyhzcsRUNyQJGE
pan2pan-02:  XTS5vXkQbGLEwaye3ZsLAtMMEe6tkh724nr2zoGHHeAUCsvVeywvc
pan2pan-03:  XTS5H3qwDsnjm8yoiN1CAQg6LKTnSNuXZDePeGAQSa5CiALSFRFQ8
pan2pan-04:  XTS4u3cQJNLS9jDN1mCM9ynLNHQV9PuEVfwA2R95XnV7ZDNjJL89z
pan2pan-05:  XTS7qHJeGEfMjogPuAnDZ6Vte9nAG7y4hHsM6iXF3aDmN52qz7foT


Name:
Location: Winnipeg, Canada

Hardware:
AMD fx6300
8 GB ddr3 1600mhz ram
500GB HD


Software:

OS Ubuntu server 14.04
Title: Re: Initial delegates, let's get ready!
Post by: werneo on June 08, 2014, 12:24:42 am
Enjoy!  Looks too fiddly for a user like me, I just need an application I can install, configure and run.
Yes  +5%
Title: Re: Initial delegates, let's get ready!
Post by: muse-umum on June 08, 2014, 12:38:29 am
really? exposing the delegates’ IP addresses?
Title: Re: Initial delegates, let's get ready!
Post by: Stan on June 08, 2014, 12:47:22 am
Enjoy!  Looks too fiddly for a user like me, I just need an application I can install, configure and run.
Yes  +5%

Sounds like a business opportunity for some entrepreneur. 

They are everywhere in this ecosystem right now!

Pay attention and grab your niche!
Title: Re: Initial delegates, let's get ready!
Post by: toast on June 08, 2014, 12:51:48 am
really? exposing the delegates’ IP addresses?

Wow, good point... I was thinking about how we need public seed nodes but we absolutely do not need all IPs. Editing OP now


Quote
got the following error while trying to run ./bitshares_client under ubuntu14.04.  Does it caused by testnet is not running ?

We had a bad checkin, sorry. Wipe data dir and try again.
But yes, there is no test net.
Title: Re: Initial delegates, let's get ready!
Post by: bytemaster on June 08, 2014, 12:53:05 am
Working on setting up the latest test net now.
Title: Re: Initial delegates, let's get ready!
Post by: toast on June 08, 2014, 12:54:05 am
Enjoy!  Looks too fiddly for a user like me, I just need an application I can install, configure and run.
Yes  +5%

Sounds like a business opportunity for some entrepreneur. 

They are everywhere in this ecosystem right now!

Pay attention and grab your niche!

Preempting Adam's "there's no incentive, invictus hogging all the AGS"
Today we came up with a model that's gonna incentive the hell out of infrastructure development. Hang tight folks!
Title: Re: Initial delegates, let's get ready!
Post by: zhangweis on June 08, 2014, 12:56:14 am
Node: 1 Core CPU/2G memory/20G SSD
Location: Qingdao, China

Public keys:
zhangweis-delegate-1:XTS6sSu1DhZUxpnoLz1wYvwsowUQpa4zyHFkqo972fKnU6xrEKVx8
zhangweis-delegate-2:XTS7CoMc1xHodpiVYS8gukQRhmrpxaBEz7oMaUy434HBLbJegtFo1
zhangweis-delegate-3:XTS7kcfTvho6h7juwajcNxBQA9rmiqd5iSFMZYywwbWRk9wqjo2Np
zhangweis-delegate-4:XTS6yyGEujvofqgQRfwvwWxMjZiFJwE4kBE1BpXtGpmhZ8aC58Dmb
zhangweis-delegate-5:XTS4yrt2mFvEcaNCD3HVYiDgWcS5jVpf3R9MfnTh6W3v3Y1W4vGrA
Title: Re: Initial delegates, let's get ready!
Post by: alt on June 08, 2014, 01:14:10 am
I think the delicated node should seperate from seed node. avoid attack like ddos. security is the most important for delicated node.
Title: Re: Initial delegates, let's get ready!
Post by: Stan on June 08, 2014, 01:18:46 am
Enjoy!  Looks too fiddly for a user like me, I just need an application I can install, configure and run.
Yes  +5%

Sounds like a business opportunity for some entrepreneur. 

They are everywhere in this ecosystem right now!

Pay attention and grab your niche!

Preempting Adam's "there's no incentive, invictus hogging all the AGS"
Today we came up with a model that's gonna incentive the hell out of infrastructure development. Hang tight folks!

"You can't win Darth.
When I get my Delegate seat
I shall become more powerful than you can possibly imagine."

(http://2.bp.blogspot.com/_bEpHck_hxoM/Sxw5PbzyYPI/AAAAAAAAAnE/u51CCMMib6g/s400/05_08_2006_11.jpg)

Delegate positions will be far more significant roles than is yet foreseen in the minds of men.

Prepare now, for there remains but little time.
Title: Re: Initial delegates, let's get ready!
Post by: puppies on June 08, 2014, 01:20:58 am
I'm not sure I count as qualified.  I'd like to give it a shot though.

 (I'm not sure what ports are open.  I can always googlefu it after work, but I'm on my lunch hour.)
toast edit: I removed your IP because I'm dumb and shouldn't have asked for it

Its running on a digital ocean droplet with 8GB of ram and 4cpus.

Currently based in New York, but I would gladly move it to Amsterdam, Singapore, or San Francisco if that was better for the network. 

Keys:
1: XTS8UTxLFKWaL2aFLxhwNC9C1JnTRrtDSpKTeAvB9yqNavVfFRkQ1
2: XTS5LGPcabhmv2Y3rpT5YP1Ba8nUFoU1P2GFrth81Za9TFV78EjBc
3: XTS6s5vsTDMJm429keEXJi4RSAHhgm2mf6GGuV7LnKvZYfPMeXFS1
4: XTS8djaCmGAU6VhQ6Ri1VEyr187cVaYar62if72rvTtUwNkvPCvqG
5: XTS6urf3pgJk15kWE24h5k8SwNrWn1Uq7JTbA2brfviZmmeLC9VPw

I'm not the most technically sound, but I've been able to get the previous test nets up and running just fine.  (I can follow simple directions)
Title: Re: Initial delegates, let's get ready!
Post by: alt on June 08, 2014, 02:18:43 am
Location: ShangHai, China
os: ubuntu
cpu: Intel I5-4200U
mem: 4G
alt-delegate-1: XTS57VJ3pc85WWJWCwNzPBcwNHEqHstavbhgFfHgc8nTmCchXGJAM
alt-delegate-2: XTS613zBdL38aPmLyMPtiTxKHnqiD7eiFZUsAFdVPzZmx4aZ8c8wq
alt-delegate-3: XTS5siws5HRdVw8XYjPtq1S2536ahueJXcrXsjhnk3PAffhpkYzZd
alt-delegate-4: XTS5iUxjeTmcdb2MrZBD32n73fLP1P1gBY4peWdaj1AZ6NrbBmr3y
alt-delegate-5: XTS72LSQVoJnQoMgeBrjihzAS6YLGWdhqRdD8NtLb6ukgoLL9GxLa
Title: Re: Initial delegates, let's get ready!
Post by: toast on June 08, 2014, 02:23:16 am
Another test net is up right now - just a test test network, we will do the real dry-run when we have more delegates

puppies, emski, your 10 keys are registered as initial delegates.
sfinder, for some reason Dan didn't see your post. Whoops. You'll get into the real dry run with everyone else.

puppies and emski should:

1) Pull latest (+ git submodule update) and build
2) Wipe data dir
3) "wallet_create" / "wallet_unlock 9999999"
4) "wallet_import_private_key <WIF_PRIVATE_KEY>" on each key (other readers: you must "wallet_account_create" first if you are not hard-coded delegate)
5) "rescan"

Leave it running for a while (50 minutes worst case)

6) "blockchain_get_delegates"  -> see the names of all your delegats
7) "blockchain_get_account_record <delegate_name>"

"blocks_produced" should be more than 0.
"blocks_missed" will be big but should stop increasing after you import your keys
Title: Re: Initial delegates, let's get ready!
Post by: spartako on June 08, 2014, 02:24:14 am
Node specs:
* Server located in Germany.
* 32G RAM
* 4 core Intel Xeon E3-1230v2
* 256 GB SSD
* 2 TB SATA
* Ubuntu 12.04 LTS

Keys:
spartako-delegate-1: XTS6DDBA3URydxP2EPPtTwJ6JcSV28ut7ukN2HCVgrDuH4UCxF9Jv
spartako-delegate-2: XTS8LLDp6tZzh4bt5mBJXrigaff76xJCHzU1uqJrEryJpiZFcW3Ac
spartako-delegate-3: XTS7CGASnpNRTnfcqMhTTGAgbmpstVS3U3mWfHoAmwAXQaer7BvUD
spartako-delegate-4: XTS6o9KsYFpuPLQy9HCZGJrsxhnSFrv4DN4C3XNmb3kknFXikBBPP
spartako-delegate-5: XTS7xP4je99nWGnbNC2bKxNpTK5661iX4oLnj8Qije6KgxAWb5H5k

 
Title: Re: Initial delegates, let's get ready!
Post by: bitcoinerS on June 08, 2014, 02:28:55 am
latest git pull.


Code: [Select]

~/local/bitshares_toolkit/programs/client$ rm ../../data/ -rf

./bitshares_client
================================================================
=                                                              =
=             Welcome to BitShares XTS                         =
=                                                              =
=  This software is in alpha testing and is not suitable for   =
=  real monetary transactions or trading.  Use at your own     =
=  risk.                                                       =
=                                                              =
=  Type 'help' for usage information.                          =
================================================================
Logging to file "/home/slava/.BitSharesXTS/default.log"
Logging RPC to file "/home/slava/.BitSharesXTS/rpc.log"
Loading config "/home/slava/.BitSharesXTS/config.json"
{
  "rpc": {
    "rpc_user": "",
    "rpc_password": "",
    "rpc_endpoint": "127.0.0.1:0",
    "httpd_endpoint": "127.0.0.1:0",
    "htdocs": "./htdocs"
  },
  "default_peers": [
    "107.170.30.182:8764"
  ],
  "ignore_console": false
}
Loading blockchain from "/home/slava/.BitSharesXTS/chain"
Using genesis block from file "/home/slava/local/bitshares_toolkit/programs/client/genesis.json"
Initializing genesis state
------------ error --------------
10
total_votes == total.amount:
    {"total_votes":999999999999994,"total_shares":{"amount":1999999999999988,"asset_id":0}}
    th_a  chain_database.cpp:1681 sanity_check

    {}
    th_a  chain_database.cpp:1688 sanity_check

    {}
    th_a  chain_database.cpp:1442 initialize_genesis

    {"data_dir":"/home/slava/.BitSharesXTS/chain"}
    th_a  chain_database.cpp:864 open

    {"data_dir":"/home/slava/.BitSharesXTS","genesis_dat":"/home/slava/local/bitshares_toolkit/programs/client/genesis.json"}
    th_a  client.cpp:325 open
Title: Re: Initial delegates, let's get ready!
Post by: toast on June 08, 2014, 02:30:25 am
latest git pull.


Code: [Select]

~/local/bitshares_toolkit/programs/client$ rm ../../data/ -rf

./bitshares_client
================================================================
=                                                              =
=             Welcome to BitShares XTS                         =
=                                                              =
=  This software is in alpha testing and is not suitable for   =
=  real monetary transactions or trading.  Use at your own     =
=  risk.                                                       =
=                                                              =
=  Type 'help' for usage information.                          =
================================================================
Logging to file "/home/slava/.BitSharesXTS/default.log"
Logging RPC to file "/home/slava/.BitSharesXTS/rpc.log"
Loading config "/home/slava/.BitSharesXTS/config.json"
{
  "rpc": {
    "rpc_user": "",
    "rpc_password": "",
    "rpc_endpoint": "127.0.0.1:0",
    "httpd_endpoint": "127.0.0.1:0",
    "htdocs": "./htdocs"
  },
  "default_peers": [
    "107.170.30.182:8764"
  ],
  "ignore_console": false
}
Loading blockchain from "/home/slava/.BitSharesXTS/chain"
Using genesis block from file "/home/slava/local/bitshares_toolkit/programs/client/genesis.json"
Initializing genesis state
------------ error --------------
10
total_votes == total.amount:
    {"total_votes":999999999999994,"total_shares":{"amount":1999999999999988,"asset_id":0}}
    th_a  chain_database.cpp:1681 sanity_check

    {}
    th_a  chain_database.cpp:1688 sanity_check

    {}
    th_a  chain_database.cpp:1442 initialize_genesis

    {"data_dir":"/home/slava/.BitSharesXTS/chain"}
    th_a  chain_database.cpp:864 open

    {"data_dir":"/home/slava/.BitSharesXTS","genesis_dat":"/home/slava/local/bitshares_toolkit/programs/client/genesis.json"}
    th_a  client.cpp:325 open

Did you wipe your data dir?
Did you "git submodule update"?
Title: Re: Initial delegates, let's get ready!
Post by: sfinder on June 08, 2014, 02:35:42 am
i did remove data dir but did not fix the problem

latest git pull.


Code: [Select]

~/local/bitshares_toolkit/programs/client$ rm ../../data/ -rf

./bitshares_client
================================================================
=                                                              =
=             Welcome to BitShares XTS                         =
=                                                              =
=  This software is in alpha testing and is not suitable for   =
=  real monetary transactions or trading.  Use at your own     =
=  risk.                                                       =
=                                                              =
=  Type 'help' for usage information.                          =
================================================================
Logging to file "/home/slava/.BitSharesXTS/default.log"
Logging RPC to file "/home/slava/.BitSharesXTS/rpc.log"
Loading config "/home/slava/.BitSharesXTS/config.json"
{
  "rpc": {
    "rpc_user": "",
    "rpc_password": "",
    "rpc_endpoint": "127.0.0.1:0",
    "httpd_endpoint": "127.0.0.1:0",
    "htdocs": "./htdocs"
  },
  "default_peers": [
    "107.170.30.182:8764"
  ],
  "ignore_console": false
}
Loading blockchain from "/home/slava/.BitSharesXTS/chain"
Using genesis block from file "/home/slava/local/bitshares_toolkit/programs/client/genesis.json"
Initializing genesis state
------------ error --------------
10
total_votes == total.amount:
    {"total_votes":999999999999994,"total_shares":{"amount":1999999999999988,"asset_id":0}}
    th_a  chain_database.cpp:1681 sanity_check

    {}
    th_a  chain_database.cpp:1688 sanity_check

    {}
    th_a  chain_database.cpp:1442 initialize_genesis

    {"data_dir":"/home/slava/.BitSharesXTS/chain"}
    th_a  chain_database.cpp:864 open

    {"data_dir":"/home/slava/.BitSharesXTS","genesis_dat":"/home/slava/local/bitshares_toolkit/programs/client/genesis.json"}
    th_a  client.cpp:325 open

Did you wipe your data dir?
Did you "git submodule update"?
Title: Re: Initial delegates, let's get ready!
Post by: bitder on June 08, 2014, 02:40:49 am
Node spec: (currently running on Ubuntu 14.04 VM in Canada - can upgrade to dedicated HW or move to AWS. Will size as required)
1.5GB
1 vCPU

bitder-delegate-1: XTS6qTT13ykM2kshakrFS4M4o4TcpNPhkQuV1h8dL2UJbZyQU2yMd
bitder-delegate-2: XTS6SoXmqo5vdHYNXvyjxUoMQjeFFj2kXQHJKG4sK1JCESdmgJ7rt
bitder-delegate-3: XTS5BwuZQfFMpktrVsXLUDQxgnXg3iVY4EVQMbd1Y4BNz145kQdh6
bitder-delegate-4: XTS5TQbUB5UBmEG9ATLBhHe1Aw4AbctmTNji5QgHv9SFXX7rJAK64
bitder-delegate-5: XTS8Tq5MvRyU7PMBAMXCMRXTqNvfUzoHr9jK1Bo6K245FKZ5BFJxM
Title: Re: Initial delegates, let's get ready!
Post by: bitder on June 08, 2014, 02:50:33 am
sfinder, try
$ rm -rf ~/.BitSharesXTS


i did remove data dir but did not fix the problem

latest git pull.


Code: [Select]

~/local/bitshares_toolkit/programs/client$ rm ../../data/ -rf

./bitshares_client
================================================================
=                                                              =
=             Welcome to BitShares XTS                         =
=                                                              =
=  This software is in alpha testing and is not suitable for   =
=  real monetary transactions or trading.  Use at your own     =
=  risk.                                                       =
=                                                              =
=  Type 'help' for usage information.                          =
================================================================
Logging to file "/home/slava/.BitSharesXTS/default.log"
Logging RPC to file "/home/slava/.BitSharesXTS/rpc.log"
Loading config "/home/slava/.BitSharesXTS/config.json"
{
  "rpc": {
    "rpc_user": "",
    "rpc_password": "",
    "rpc_endpoint": "127.0.0.1:0",
    "httpd_endpoint": "127.0.0.1:0",
    "htdocs": "./htdocs"
  },
  "default_peers": [
    "107.170.30.182:8764"
  ],
  "ignore_console": false
}
Loading blockchain from "/home/slava/.BitSharesXTS/chain"
Using genesis block from file "/home/slava/local/bitshares_toolkit/programs/client/genesis.json"
Initializing genesis state
------------ error --------------
10
total_votes == total.amount:
    {"total_votes":999999999999994,"total_shares":{"amount":1999999999999988,"asset_id":0}}
    th_a  chain_database.cpp:1681 sanity_check

    {}
    th_a  chain_database.cpp:1688 sanity_check

    {}
    th_a  chain_database.cpp:1442 initialize_genesis

    {"data_dir":"/home/slava/.BitSharesXTS/chain"}
    th_a  chain_database.cpp:864 open

    {"data_dir":"/home/slava/.BitSharesXTS","genesis_dat":"/home/slava/local/bitshares_toolkit/programs/client/genesis.json"}
    th_a  client.cpp:325 open

Did you wipe your data dir?
Did you "git submodule update"?
Title: Re: Initial delegates, let's get ready!
Post by: sfinder on June 08, 2014, 02:54:15 am

i have removed data dir but still not fixing my problem



daniel@ubuntu:~/bitshares_toolkit/programs/client$ rm -rf /home/daniel/.BitSharesXTS
daniel@ubuntu:~/bitshares_toolkit/programs/client$ ./bitshares_client --server  ================================================================
=                                                              =
=             Welcome to BitShares XTS                         =
=                                                              =
=  This software is in alpha testing and is not suitable for   =
=  real monetary transactions or trading.  Use at your own     =
=  risk.                                                       =
=                                                              =
=  Type 'help' for usage information.                          =
================================================================
Creating default config file "/home/daniel/.BitSharesXTS/config.json"
Logging to file "/home/daniel/.BitSharesXTS/default.log"
Logging RPC to file "/home/daniel/.BitSharesXTS/rpc.log"
{
  "rpc": {
    "rpc_user": "",
    "rpc_password": "",
    "rpc_endpoint": "127.0.0.1:0",
    "httpd_endpoint": "127.0.0.1:0",
    "htdocs": "./htdocs"
  },
  "default_peers": [
    "107.170.30.182:8764"
  ],
  "ignore_console": false,
  "logging": {
    "includes": [],
    "appenders": [{
        "name": "default",
        "type": "file",
        "args": {
          "format": "${timestamp} ${thread_name} ${context} ${file}:${line} ${method} ${level}]  ${message}",
          "filename": "/home/daniel/.BitSharesXTS/default.log",
          "flush": true,
          "truncate": false
        },
        "enabled": true
      },{
        "name": "rpc",
        "type": "file",
        "args": {
          "format": "${timestamp} ${thread_name} ${context} ${file}:${line} ${method} ${level}]  ${message}",
          "filename": "/home/daniel/.BitSharesXTS/rpc.log",
          "flush": true,
          "truncate": false
        },
        "enabled": true
      }
    ],
    "loggers": [{
        "name": "default",
        "parent": null,
        "level": "debug",
        "enabled": true,
        "additivity": false,
        "appenders": [
          "default"
        ]
      },{
        "name": "rpc",
        "parent": null,
        "level": "debug",
        "enabled": true,
        "additivity": false,
        "appenders": [
          "rpc"
        ]
      }
    ]
  }
}
Loading blockchain from "/home/daniel/.BitSharesXTS/chain"
Using genesis block from file "/home/daniel/bitshares_toolkit/programs/client/genesis.json"
------------ error --------------
10
fc::sha256::hash( response.body.data(), response.body.size() ) == check:
    {}
    th_a  client.cpp:325 open

    {"data_dir":"/home/daniel/.BitSharesXTS"}
    th_a  client.cpp:341 open
daniel@ubuntu:~/bitshares_toolkit/programs/client$ ^C
daniel@ubuntu:~/bitshares_toolkit/programs/client$ rm -rf /home/daniel/.BitSharesXTS






sfinder, try
$ rm -rf ~/.BitSharesXTS


i did remove data dir but did not fix the problem

latest git pull.


Code: [Select]

~/local/bitshares_toolkit/programs/client$ rm ../../data/ -rf

./bitshares_client
================================================================
=                                                              =
=             Welcome to BitShares XTS                         =
=                                                              =
=  This software is in alpha testing and is not suitable for   =
=  real monetary transactions or trading.  Use at your own     =
=  risk.                                                       =
=                                                              =
=  Type 'help' for usage information.                          =
================================================================
Logging to file "/home/slava/.BitSharesXTS/default.log"
Logging RPC to file "/home/slava/.BitSharesXTS/rpc.log"
Loading config "/home/slava/.BitSharesXTS/config.json"
{
  "rpc": {
    "rpc_user": "",
    "rpc_password": "",
    "rpc_endpoint": "127.0.0.1:0",
    "httpd_endpoint": "127.0.0.1:0",
    "htdocs": "./htdocs"
  },
  "default_peers": [
    "107.170.30.182:8764"
  ],
  "ignore_console": false
}
Loading blockchain from "/home/slava/.BitSharesXTS/chain"
Using genesis block from file "/home/slava/local/bitshares_toolkit/programs/client/genesis.json"
Initializing genesis state
------------ error --------------
10
total_votes == total.amount:
    {"total_votes":999999999999994,"total_shares":{"amount":1999999999999988,"asset_id":0}}
    th_a  chain_database.cpp:1681 sanity_check

    {}
    th_a  chain_database.cpp:1688 sanity_check

    {}
    th_a  chain_database.cpp:1442 initialize_genesis

    {"data_dir":"/home/slava/.BitSharesXTS/chain"}
    th_a  chain_database.cpp:864 open

    {"data_dir":"/home/slava/.BitSharesXTS","genesis_dat":"/home/slava/local/bitshares_toolkit/programs/client/genesis.json"}
    th_a  client.cpp:325 open

Did you wipe your data dir?
Did you "git submodule update"?
Title: Re: Initial delegates, let's get ready!
Post by: bitder on June 08, 2014, 02:58:21 am
$ git fetch
$ git rebase
$ git submodule update
$ make
$ rm -rf ~/.BitSharesXTS



i have removed data dir but still not fixing my problem



daniel@ubuntu:~/bitshares_toolkit/programs/client$ rm -rf /home/daniel/.BitSharesXTS
daniel@ubuntu:~/bitshares_toolkit/programs/client$ ./bitshares_client --server  ================================================================
=                                                              =
=             Welcome to BitShares XTS                         =
=                                                              =
=  This software is in alpha testing and is not suitable for   =
=  real monetary transactions or trading.  Use at your own     =
=  risk.                                                       =
=                                                              =
=  Type 'help' for usage information.                          =
================================================================
Creating default config file "/home/daniel/.BitSharesXTS/config.json"
Logging to file "/home/daniel/.BitSharesXTS/default.log"
Logging RPC to file "/home/daniel/.BitSharesXTS/rpc.log"
{
  "rpc": {
    "rpc_user": "",
    "rpc_password": "",
    "rpc_endpoint": "127.0.0.1:0",
    "httpd_endpoint": "127.0.0.1:0",
    "htdocs": "./htdocs"
  },
  "default_peers": [
    "107.170.30.182:8764"
  ],
  "ignore_console": false,
  "logging": {
    "includes": [],
    "appenders": [{
        "name": "default",
        "type": "file",
        "args": {
          "format": "${timestamp} ${thread_name} ${context} ${file}:${line} ${method} ${level}]  ${message}",
          "filename": "/home/daniel/.BitSharesXTS/default.log",
          "flush": true,
          "truncate": false
        },
        "enabled": true
      },{
        "name": "rpc",
        "type": "file",
        "args": {
          "format": "${timestamp} ${thread_name} ${context} ${file}:${line} ${method} ${level}]  ${message}",
          "filename": "/home/daniel/.BitSharesXTS/rpc.log",
          "flush": true,
          "truncate": false
        },
        "enabled": true
      }
    ],
    "loggers": [{
        "name": "default",
        "parent": null,
        "level": "debug",
        "enabled": true,
        "additivity": false,
        "appenders": [
          "default"
        ]
      },{
        "name": "rpc",
        "parent": null,
        "level": "debug",
        "enabled": true,
        "additivity": false,
        "appenders": [
          "rpc"
        ]
      }
    ]
  }
}
Loading blockchain from "/home/daniel/.BitSharesXTS/chain"
Using genesis block from file "/home/daniel/bitshares_toolkit/programs/client/genesis.json"
------------ error --------------
10
fc::sha256::hash( response.body.data(), response.body.size() ) == check:
    {}
    th_a  client.cpp:325 open

    {"data_dir":"/home/daniel/.BitSharesXTS"}
    th_a  client.cpp:341 open
daniel@ubuntu:~/bitshares_toolkit/programs/client$ ^C
daniel@ubuntu:~/bitshares_toolkit/programs/client$ rm -rf /home/daniel/.BitSharesXTS






sfinder, try
$ rm -rf ~/.BitSharesXTS


i did remove data dir but did not fix the problem

latest git pull.


Code: [Select]

~/local/bitshares_toolkit/programs/client$ rm ../../data/ -rf

./bitshares_client
================================================================
=                                                              =
=             Welcome to BitShares XTS                         =
=                                                              =
=  This software is in alpha testing and is not suitable for   =
=  real monetary transactions or trading.  Use at your own     =
=  risk.                                                       =
=                                                              =
=  Type 'help' for usage information.                          =
================================================================
Logging to file "/home/slava/.BitSharesXTS/default.log"
Logging RPC to file "/home/slava/.BitSharesXTS/rpc.log"
Loading config "/home/slava/.BitSharesXTS/config.json"
{
  "rpc": {
    "rpc_user": "",
    "rpc_password": "",
    "rpc_endpoint": "127.0.0.1:0",
    "httpd_endpoint": "127.0.0.1:0",
    "htdocs": "./htdocs"
  },
  "default_peers": [
    "107.170.30.182:8764"
  ],
  "ignore_console": false
}
Loading blockchain from "/home/slava/.BitSharesXTS/chain"
Using genesis block from file "/home/slava/local/bitshares_toolkit/programs/client/genesis.json"
Initializing genesis state
------------ error --------------
10
total_votes == total.amount:
    {"total_votes":999999999999994,"total_shares":{"amount":1999999999999988,"asset_id":0}}
    th_a  chain_database.cpp:1681 sanity_check

    {}
    th_a  chain_database.cpp:1688 sanity_check

    {}
    th_a  chain_database.cpp:1442 initialize_genesis

    {"data_dir":"/home/slava/.BitSharesXTS/chain"}
    th_a  chain_database.cpp:864 open

    {"data_dir":"/home/slava/.BitSharesXTS","genesis_dat":"/home/slava/local/bitshares_toolkit/programs/client/genesis.json"}
    th_a  client.cpp:325 open

Did you wipe your data dir?
Did you "git submodule update"?
Title: Re: Initial delegates, let's get ready!
Post by: toast on June 08, 2014, 03:00:15 am
sfinder, can you type command "about" and tell us what your revision is?

Code: [Select]
"bitshares_toolkit_revision": "..."
"fc_revision": "..."
Title: Re: Initial delegates, let's get ready!
Post by: bitcoinerS on June 08, 2014, 03:00:39 am
I am not entirely sure which data directory needs to be removed. I deleted

~/local/bitshares_toolkit/programs/client$ rm ../../data/ -rf
rm ~/.BitSharesXTS/ -rf

sfinder, try
$ rm -rf ~/.BitSharesXTS


i did remove data dir but did not fix the problem

latest git pull.


Code: [Select]

~/local/bitshares_toolkit/programs/client$ rm ../../data/ -rf

./bitshares_client
================================================================
=                                                              =
=             Welcome to BitShares XTS                         =
=                                                              =
=  This software is in alpha testing and is not suitable for   =
=  real monetary transactions or trading.  Use at your own     =
=  risk.                                                       =
=                                                              =
=  Type 'help' for usage information.                          =
================================================================
Logging to file "/home/slava/.BitSharesXTS/default.log"
Logging RPC to file "/home/slava/.BitSharesXTS/rpc.log"
Loading config "/home/slava/.BitSharesXTS/config.json"
{
  "rpc": {
    "rpc_user": "",
    "rpc_password": "",
    "rpc_endpoint": "127.0.0.1:0",
    "httpd_endpoint": "127.0.0.1:0",
    "htdocs": "./htdocs"
  },
  "default_peers": [
    "107.170.30.182:8764"
  ],
  "ignore_console": false
}
Loading blockchain from "/home/slava/.BitSharesXTS/chain"
Using genesis block from file "/home/slava/local/bitshares_toolkit/programs/client/genesis.json"
Initializing genesis state
------------ error --------------
10
total_votes == total.amount:
    {"total_votes":999999999999994,"total_shares":{"amount":1999999999999988,"asset_id":0}}
    th_a  chain_database.cpp:1681 sanity_check

    {}
    th_a  chain_database.cpp:1688 sanity_check

    {}
    th_a  chain_database.cpp:1442 initialize_genesis

    {"data_dir":"/home/slava/.BitSharesXTS/chain"}
    th_a  chain_database.cpp:864 open

    {"data_dir":"/home/slava/.BitSharesXTS","genesis_dat":"/home/slava/local/bitshares_toolkit/programs/client/genesis.json"}
    th_a  client.cpp:325 open

Did you wipe your data dir?
Did you "git submodule update"?
Title: Re: Initial delegates, let's get ready!
Post by: alt on June 08, 2014, 03:03:53 am
you need update your code


i have removed data dir but still not fixing my problem



daniel@ubuntu:~/bitshares_toolkit/programs/client$ rm -rf /home/daniel/.BitSharesXTS
daniel@ubuntu:~/bitshares_toolkit/programs/client$ ./bitshares_client --server  ================================================================
=                                                              =
=             Welcome to BitShares XTS                         =
=                                                              =
=  This software is in alpha testing and is not suitable for   =
=  real monetary transactions or trading.  Use at your own     =
=  risk.                                                       =
=                                                              =
=  Type 'help' for usage information.                          =
================================================================
Creating default config file "/home/daniel/.BitSharesXTS/config.json"
Logging to file "/home/daniel/.BitSharesXTS/default.log"
Logging RPC to file "/home/daniel/.BitSharesXTS/rpc.log"
{
  "rpc": {
    "rpc_user": "",
    "rpc_password": "",
    "rpc_endpoint": "127.0.0.1:0",
    "httpd_endpoint": "127.0.0.1:0",
    "htdocs": "./htdocs"
  },
  "default_peers": [
    "107.170.30.182:8764"
  ],
  "ignore_console": false,
  "logging": {
    "includes": [],
    "appenders": [{
        "name": "default",
        "type": "file",
        "args": {
          "format": "${timestamp} ${thread_name} ${context} ${file}:${line} ${method} ${level}]  ${message}",
          "filename": "/home/daniel/.BitSharesXTS/default.log",
          "flush": true,
          "truncate": false
        },
        "enabled": true
      },{
        "name": "rpc",
        "type": "file",
        "args": {
          "format": "${timestamp} ${thread_name} ${context} ${file}:${line} ${method} ${level}]  ${message}",
          "filename": "/home/daniel/.BitSharesXTS/rpc.log",
          "flush": true,
          "truncate": false
        },
        "enabled": true
      }
    ],
    "loggers": [{
        "name": "default",
        "parent": null,
        "level": "debug",
        "enabled": true,
        "additivity": false,
        "appenders": [
          "default"
        ]
      },{
        "name": "rpc",
        "parent": null,
        "level": "debug",
        "enabled": true,
        "additivity": false,
        "appenders": [
          "rpc"
        ]
      }
    ]
  }
}
Loading blockchain from "/home/daniel/.BitSharesXTS/chain"
Using genesis block from file "/home/daniel/bitshares_toolkit/programs/client/genesis.json"
------------ error --------------
10
fc::sha256::hash( response.body.data(), response.body.size() ) == check:
    {}
    th_a  client.cpp:325 open

    {"data_dir":"/home/daniel/.BitSharesXTS"}
    th_a  client.cpp:341 open
daniel@ubuntu:~/bitshares_toolkit/programs/client$ ^C
daniel@ubuntu:~/bitshares_toolkit/programs/client$ rm -rf /home/daniel/.BitSharesXTS






sfinder, try
$ rm -rf ~/.BitSharesXTS


i did remove data dir but did not fix the problem

latest git pull.


Code: [Select]

~/local/bitshares_toolkit/programs/client$ rm ../../data/ -rf

./bitshares_client
================================================================
=                                                              =
=             Welcome to BitShares XTS                         =
=                                                              =
=  This software is in alpha testing and is not suitable for   =
=  real monetary transactions or trading.  Use at your own     =
=  risk.                                                       =
=                                                              =
=  Type 'help' for usage information.                          =
================================================================
Logging to file "/home/slava/.BitSharesXTS/default.log"
Logging RPC to file "/home/slava/.BitSharesXTS/rpc.log"
Loading config "/home/slava/.BitSharesXTS/config.json"
{
  "rpc": {
    "rpc_user": "",
    "rpc_password": "",
    "rpc_endpoint": "127.0.0.1:0",
    "httpd_endpoint": "127.0.0.1:0",
    "htdocs": "./htdocs"
  },
  "default_peers": [
    "107.170.30.182:8764"
  ],
  "ignore_console": false
}
Loading blockchain from "/home/slava/.BitSharesXTS/chain"
Using genesis block from file "/home/slava/local/bitshares_toolkit/programs/client/genesis.json"
Initializing genesis state
------------ error --------------
10
total_votes == total.amount:
    {"total_votes":999999999999994,"total_shares":{"amount":1999999999999988,"asset_id":0}}
    th_a  chain_database.cpp:1681 sanity_check

    {}
    th_a  chain_database.cpp:1688 sanity_check

    {}
    th_a  chain_database.cpp:1442 initialize_genesis

    {"data_dir":"/home/slava/.BitSharesXTS/chain"}
    th_a  chain_database.cpp:864 open

    {"data_dir":"/home/slava/.BitSharesXTS","genesis_dat":"/home/slava/local/bitshares_toolkit/programs/client/genesis.json"}
    th_a  client.cpp:325 open

Did you wipe your data dir?
Did you "git submodule update"?
Title: Re: Initial delegates, let's get ready!
Post by: bitcoinerS on June 08, 2014, 03:11:38 am
I am getting a compilation error trying to build on clean Ubuntu 14.04 server

Code: [Select]
Building CXX object libraries/net/CMakeFiles/bts_net.dir/node.cpp.o
In file included from /root/bitshares_toolkit/libraries/client/include/bts/client/messages.hpp:3:0,
                 from /root/bitshares_toolkit/libraries/net/node.cpp:32:
/root/bitshares_toolkit/libraries/client/include/bts/client/client.hpp:6:34: fatal error: bts/api/common_api.hpp: No such file or directory
 #include <bts/api/common_api.hpp>
                                  ^
compilation terminated.
make[2]: *** [libraries/net/CMakeFiles/bts_net.dir/node.cpp.o] Error 1
make[1]: *** [libraries/net/CMakeFiles/bts_net.dir/all] Error 2
make: *** [all] Error 2
Title: Re: Initial delegates, let's get ready!
Post by: alt on June 08, 2014, 03:15:50 am
this file is generated from json file.
something is wrong before this error.
the easy way is make clean and rebuild
I am getting a compilation error trying to build on clean Ubuntu 14.04 server

Code: [Select]
Building CXX object libraries/net/CMakeFiles/bts_net.dir/node.cpp.o
In file included from /root/bitshares_toolkit/libraries/client/include/bts/client/messages.hpp:3:0,
                 from /root/bitshares_toolkit/libraries/net/node.cpp:32:
/root/bitshares_toolkit/libraries/client/include/bts/client/client.hpp:6:34: fatal error: bts/api/common_api.hpp: No such file or directory
 #include <bts/api/common_api.hpp>
                                  ^
compilation terminated.
make[2]: *** [libraries/net/CMakeFiles/bts_net.dir/node.cpp.o] Error 1
make[1]: *** [libraries/net/CMakeFiles/bts_net.dir/all] Error 2
make: *** [all] Error 2
Title: Re: Initial delegates, let's get ready!
Post by: welk1n on June 08, 2014, 03:18:20 am
wei (unlocked) >>> wallet_import_private_key 5K1D1semMJdX6i4RSiWXHYLHhm7RhRXup2KswGzeEan3oqd2TY5 "welk1n-a"
10
is_valid_account( account_name ):
    {}
    th_a  wallet.cpp:784 import_private_key

    {"account_name":"welk1n-a"}
    th_a  wallet.cpp:811 import_private_key

    {"account_name":"welk1n-a"}
    th_a  wallet.cpp:830 import_wif_private_key

    {}
    th_a  common_api_client.cpp:202 wallet_import_private_key

    {"command":"wallet_import_private_key"}
    th_a  cli.cpp:574 execute_command
Title: Re: Initial delegates, let's get ready!
Post by: alt on June 08, 2014, 03:21:19 am
create the account first

wei (unlocked) >>> wallet_import_private_key 5K1D1semMJdX6i4RSiWXHYLHhm7RhRXup2KswGzeEan3oqd2TY5 "welk1n-a"
10
is_valid_account( account_name ):
    {}
    th_a  wallet.cpp:784 import_private_key

    {"account_name":"welk1n-a"}
    th_a  wallet.cpp:811 import_private_key

    {"account_name":"welk1n-a"}
    th_a  wallet.cpp:830 import_wif_private_key

    {}
    th_a  common_api_client.cpp:202 wallet_import_private_key

    {"command":"wallet_import_private_key"}
    th_a  cli.cpp:574 execute_command

Title: Re: Initial delegates, let's get ready!
Post by: sfinder on June 08, 2014, 03:21:26 am
I updated the source/compiled  and  run ./bitshares_client  without -- server and following is the output . look like "wallect closed"
------------------------------------------------------------------------------------
Using genesis block from file "/home/daniel/bitshares_toolkit/programs/client/genesis.json"
Not starting RPC server, use --server to enable the RPC interface
Listening for P2P connections on port 58273
Attempting to connect to peer 107.170.30.182:8764
Attempting to connect to peer 114.215.104.153:8764
Attempting to connect to peer 84.238.140.192:8764
(wallet closed) >>>

sfinder, can you type command "about" and tell us what your revision is?

Code: [Select]
"bitshares_toolkit_revision": "..."
"fc_revision": "..."
Title: Re: Initial delegates, let's get ready!
Post by: toast on June 08, 2014, 03:22:01 am
You must create an account with that name first with "wallet_account_create welk1n-a".

Thanks, I will update instructions.

wei (unlocked) >>> wallet_import_private_key 5K1D1semMJdX6i4RSiWXHYLHhm7RhRXup2KswGzeEan3oqd2TY5 "welk1n-a"
10
is_valid_account( account_name ):
    {}
    th_a  wallet.cpp:784 import_private_key

    {"account_name":"welk1n-a"}
    th_a  wallet.cpp:811 import_private_key

    {"account_name":"welk1n-a"}
    th_a  wallet.cpp:830 import_wif_private_key

    {}
    th_a  common_api_client.cpp:202 wallet_import_private_key

    {"command":"wallet_import_private_key"}
    th_a  cli.cpp:574 execute_command

Title: Re: Initial delegates, let's get ready!
Post by: alt on June 08, 2014, 03:22:45 am
waitting for the real dry run  8)
Another test net is up right now - just a test test network, we will do the real dry-run when we have more delegates

puppies, emski, your 10 keys are registered as initial delegates.
sfinder, for some reason Dan didn't see your post. Whoops. You'll get into the real dry run with everyone else.

puppies and emski should:

1) Pull latest (+ git submodule update) and build
2) Wipe data dir
3) "wallet_create" / "wallet_unlock 9999999"
4) "wallet_import_private_key <WIF_PRIVATE_KEY>" on each key
5) "rescan"

Leave it running for a while (50 minutes worst case)

6) "blockchain_get_delegates"  -> see the names of all your delegats
7) "blockchain_get_account_record <delegate_name>"

"blocks_produced" should be more than 0.
"blocks_missed" will be big but should stop increasing after you import your keys
Title: Re: Initial delegates, let's get ready!
Post by: crazybit on June 08, 2014, 03:23:33 am
tips for those got following error.
Quote
fc::sha256::hash( response.body.data(), response.body.size() ) == check:

seems there is some issue on the checksum, the workaround is to download the genesis file from http://bitshares.org/snapshots/xt_genesis.json directly, then rename to genesis.json and place in ----data-dir path manually
Title: Re: Initial delegates, let's get ready!
Post by: bitcoinerS on June 08, 2014, 03:27:46 am
Where are instructions on setting up a delegate node?
I am setting up using a VPS server running an Ubuntu 14.04
Title: Re: Initial delegates, let's get ready!
Post by: toast on June 08, 2014, 03:30:41 am
Where are instructions on setting up a delegate node?
I am setting up using a VPS server running an Ubuntu 14.04

The first post. It's just a normal node that has a delegate key.


tips for those got following error.
Quote
fc::sha256::hash( response.body.data(), response.body.size() ) == check:

seems there is some issue on the checksum, the workaround is to download the genesis file from http://bitshares.org/snapshots/xt_genesis.json directly, then rename to genesis.json and place in ----data-dir path manually

Yup, good catch. The real genesis block will be baked into the client so this will not be an issue
Title: Re: Initial delegates, let's get ready!
Post by: sfinder on June 08, 2014, 03:34:32 am
how to run bts client ?
1)run ./bitshares_client  without -- server
 or 2) run ./bitshares_client  --server

I run  ./bitshares_client   but showing "wallet closed ". Does it mean My client is not connected with testnet?


toast, please make a step by step instruction.  I am not able to fine any instruction in details. BM may need to hire some to write test case for this testing. LOL
Title: Re: Initial delegates, let's get ready!
Post by: bitcoinerS on June 08, 2014, 03:35:29 am
I keep getting an error trying to build on Ubuntu 14.04

Code: [Select]
Built target bts_api_generator
[ 72%] Generating include/bts/api/common_api.hpp, ../rpc_stubs/common_api_rpc_server.cpp, ../rpc_stubs/common_api_rpc_client.cpp, ../rpc_stubs/common_api_client.cpp, ../rpc_stubs/include/bts/rpc_stubs/common_api_rpc_server.hpp, ../rpc_stubs/include/bts/rpc_stubs/common_api_rpc_client.hpp, ../rpc_stubs/include/bts/rpc_stubs/common_api_client.hpp, ../rpc_stubs/include/bts/rpc_stubs/common_api_overrides.ipp
terminate called after throwing an instance of 'std::runtime_error'
  what():  locale::facet::_S_create_c_locale name not valid
Aborted
make[2]: *** [libraries/api/include/bts/api/common_api.hpp] Error 134
make[1]: *** [libraries/api/CMakeFiles/bts_api.dir/all] Error 2
make: *** [all] Error 2
Title: Re: Initial delegates, let's get ready!
Post by: Xeldal on June 08, 2014, 03:36:51 am
I am getting a compilation error trying to build on clean Ubuntu 14.04 server

Code: [Select]
Building CXX object libraries/net/CMakeFiles/bts_net.dir/node.cpp.o
In file included from /root/bitshares_toolkit/libraries/client/include/bts/client/messages.hpp:3:0,
                 from /root/bitshares_toolkit/libraries/net/node.cpp:32:
/root/bitshares_toolkit/libraries/client/include/bts/client/client.hpp:6:34: fatal error: bts/api/common_api.hpp: No such file or directory
 #include <bts/api/common_api.hpp>
                                  ^
compilation terminated.
make[2]: *** [libraries/net/CMakeFiles/bts_net.dir/node.cpp.o] Error 1
make[1]: *** [libraries/net/CMakeFiles/bts_net.dir/all] Error 2
make: *** [all] Error 2

I'm getting the same errors every time.  I've started completely over 3 times now.  same results.  Ubuntu 14.04 using the following instructions: https://github.com/nmushegian/bitshares_toolkit/blob/master/BUILD_UBUNTU.md
Title: Re: Initial delegates, let's get ready!
Post by: bitcoinerS on June 08, 2014, 03:40:11 am
Please do!




toast, please make a step by step instruction. 
Title: Re: Initial delegates, let's get ready!
Post by: toast on June 08, 2014, 03:40:54 am
how to run bts client ?
1)run ./bitshares_client  without -- server
 or 2) run ./bitshares_client  --server

I run  ./bitshares_client   but showing "wallet closed ". Does it mean My client is not connected with testnet?


toast, please make a step by step instruction.  I am not able to fine any instruction in details. BM may need to hire some to write test case for this testing. LOL

You're fine, with or without --server doesn't matter. "Wallet closed" just means you have no wallet open, you can make one with wallet_create.
We'll make better instructions for the real dry run =)

I am getting a compilation error trying to build on clean Ubuntu 14.04 server

Code: [Select]
Building CXX object libraries/net/CMakeFiles/bts_net.dir/node.cpp.o
In file included from /root/bitshares_toolkit/libraries/client/include/bts/client/messages.hpp:3:0,
                 from /root/bitshares_toolkit/libraries/net/node.cpp:32:
/root/bitshares_toolkit/libraries/client/include/bts/client/client.hpp:6:34: fatal error: bts/api/common_api.hpp: No such file or directory
 #include <bts/api/common_api.hpp>
                                  ^
compilation terminated.
make[2]: *** [libraries/net/CMakeFiles/bts_net.dir/node.cpp.o] Error 1
make[1]: *** [libraries/net/CMakeFiles/bts_net.dir/all] Error 2
make: *** [all] Error 2

I'm getting the same errors every time.  I've started completely over 3 times now.  same results.  Ubuntu 14.04 using the following instructions: https://github.com/nmushegian/bitshares_toolkit/blob/master/BUILD_UBUNTU.md

Try "make clean" then "make", that's an auto-generated file
Title: Re: Initial delegates, let's get ready!
Post by: bitcoinerS on June 08, 2014, 03:48:14 am
getting an error trying to create an account

Code: [Select]
default (unlocked) >>> wallet_account_create bitcoinerS
10
is_valid_account_name( account_name ):
    {}
    th_a  wallet.cpp:634 create_account

    {"account_name":"bitcoinerS"}
    th_a  wallet.cpp:645 create_account

    {}
    th_a  common_api_client.cpp:342 wallet_account_create

    {"command":"wallet_account_create"}
    th_a  cli.cpp:574 execute_command
Title: Re: Initial delegates, let's get ready!
Post by: bitcoinerS on June 08, 2014, 03:48:48 am

Try "make clean" then "make", that's an auto-generated file

Did not help not help.

Code: [Select]
] Generating include/bts/api/common_api.hpp, ../rpc_stubs/common_api_rpc_server.cpp, ../rpc_stubs/common_api_rpc_client.cpp, ../rpc_stubs/common_api_client.cpp, ../rpc_stubs/include/bts/rpc_stubs/common_api_rpc_server.hpp, ../rpc_stubs/include/bts/rpc_stubs/common_api_rpc_client.hpp, ../rpc_stubs/include/bts/rpc_stubs/common_api_client.hpp, ../rpc_stubs/include/bts/rpc_stubs/common_api_overrides.ipp
terminate called after throwing an instance of 'std::runtime_error'
  what():  locale::facet::_S_create_c_locale name not valid
Aborted
make[2]: *** [libraries/api/include/bts/api/common_api.hpp] Error 134
make[1]: *** [libraries/api/CMakeFiles/bts_api.dir/all] Error 2
make: *** [all] Error 2
Title: Re: Initial delegates, let's get ready!
Post by: bytemaster on June 08, 2014, 03:49:25 am
getting an error trying to create an account

Code: [Select]
default (unlocked) >>> wallet_account_create bitcoinerS
10
is_valid_account_name( account_name ):
    {}
    th_a  wallet.cpp:634 create_account

    {"account_name":"bitcoinerS"}
    th_a  wallet.cpp:645 create_account

    {}
    th_a  common_api_client.cpp:342 wallet_account_create

    {"command":"wallet_account_create"}
    th_a  cli.cpp:574 execute_command

account names are all lowercase.
Title: Re: Initial delegates, let's get ready!
Post by: welk1n on June 08, 2014, 03:50:06 am
Thanks all

Note:

Location: Beijing, China
os: ubuntu
cpu: one core
mem: 2G

welk1n-d-1:XTS6f8fzmUDQp63nTYgsA2GQtvFoPvKrmTmuhkCvQUCnKUJwxTxtx
welk1n-d-2:XTS5urryfpdjZgwavKwufJ9A1d816LFaPbSQLu5eP2G76B7hbtuxj
welk1n-d-3:XTS7p56UNQLyWc3NB2yeT4VVtYhanf6wFC356c6vbfpvQ9CHUmg6X
welk1n-d-4:XTS7SDs7tmoYe96wjRzYqavAu4nehaMUTh3TbkGe9EPWNbA1P2XPA
welk1n-d-5:XTS6z7aMnBmXi7qL9uHfgWS6d1wedEpvQNTrwgeGb8h1MH9WVXtRC
Title: Re: Initial delegates, let's get ready!
Post by: bytemaster on June 08, 2014, 03:51:16 am

Try "make clean" then "make", that's an auto-generated file

Did not help not help. Getting same error.

This particular error is a race condition in the build process with the code generation.   We will need to see a larger history of the build commands to understand what is going on and why.

Attempt to build without -jN
Title: Re: Initial delegates, let's get ready!
Post by: bitcoinerS on June 08, 2014, 03:53:18 am

Attempt to build without -jN

how?
Title: Re: Initial delegates, let's get ready!
Post by: bytemaster on June 08, 2014, 03:54:51 am

Attempt to build without -jN

how?

If you just type make you are fine, I didn't know if you were attempting make -j8 to build with 8 cores.
Title: Re: Initial delegates, let's get ready!
Post by: bitcoinerS on June 08, 2014, 04:00:11 am

Attempt to build without -jN

how?

If you just type make you are fine, I didn't know if you were attempting make -j8 to build with 8 cores.

currently It does not build on clean Ubuntu 14.04 VPS server with this error:

Code: [Select]
] Generating include/bts/api/common_api.hpp, ../rpc_stubs/common_api_rpc_server.cpp, ../rpc_stubs/common_api_rpc_client.cpp, ../rpc_stubs/common_api_client.cpp, ../rpc_stubs/include/bts/rpc_stubs/common_api_rpc_server.hpp, ../rpc_stubs/include/bts/rpc_stubs/common_api_rpc_client.hpp, ../rpc_stubs/include/bts/rpc_stubs/common_api_client.hpp, ../rpc_stubs/include/bts/rpc_stubs/common_api_overrides.ipp
terminate called after throwing an instance of 'std::runtime_error'
  what():  locale::facet::_S_create_c_locale name not valid
Aborted
make[2]: *** [libraries/api/include/bts/api/common_api.hpp] Error 134
make[1]: *** [libraries/api/CMakeFiles/bts_api.dir/all] Error 2
make: *** [all] Error 2

make clean and make again does not help.
Title: Re: Initial delegates, let's get ready!
Post by: Xeldal on June 08, 2014, 04:02:55 am
Not sure if this helps.

Code: [Select]
root@xt1:~/bitshares_toolkit# make clean
root@xt1:~/bitshares_toolkit# make
[  1%] Building C object libraries/fc/vendor/easylzma/src/CMakeFiles/easylzma_static.dir/pavl                                                                                                 ov/Bcj2.c.o
[  1%] Building C object libraries/fc/vendor/easylzma/src/CMakeFiles/easylzma_static.dir/pavl                                                                                                 ov/Alloc.c.o
[  2%] Building C object libraries/fc/vendor/easylzma/src/CMakeFiles/easylzma_static.dir/pavl                                                                                                 ov/7zFile.c.o
[  2%] Building C object libraries/fc/vendor/easylzma/src/CMakeFiles/easylzma_static.dir/pavl                                                                                                 ov/7zStream.c.o
[  3%] Building C object libraries/fc/vendor/easylzma/src/CMakeFiles/easylzma_static.dir/pavl                                                                                                 ov/7zBuf.c.o
[  3%] Building C object libraries/fc/vendor/easylzma/src/CMakeFiles/easylzma_static.dir/pavl                                                                                                 ov/Bra86.c.o
[  4%] Building C object libraries/fc/vendor/easylzma/src/CMakeFiles/easylzma_static.dir/pavl                                                                                                 ov/LzmaEnc.c.o
/root/bitshares_toolkit/libraries/fc/vendor/easylzma/src/pavlov/LzmaEnc.c: In function ‘LzmaE                                                                                                 nc_Alloc’:
/root/bitshares_toolkit/libraries/fc/vendor/easylzma/src/pavlov/LzmaEnc.c:1916:8: warning: va                                                                                                 riable ‘btMode’ set but not used [-Wunused-but-set-variable]
   Bool btMode;
        ^
[  5%] Building C object libraries/fc/vendor/easylzma/src/CMakeFiles/easylzma_static.dir/pavl                                                                                                 ov/BraIA64.c.o
[  5%] Building C object libraries/fc/vendor/easylzma/src/CMakeFiles/easylzma_static.dir/pavl                                                                                                 ov/7zBuf2.c.o
[  6%] Building C object libraries/fc/vendor/easylzma/src/CMakeFiles/easylzma_static.dir/pavl                                                                                                 ov/Bra.c.o
/root/bitshares_toolkit/libraries/fc/vendor/easylzma/src/pavlov/Bra.c: In function ‘SPARC_Con                                                                                                 vert’:
/root/bitshares_toolkit/libraries/fc/vendor/easylzma/src/pavlov/Bra.c:107:25: warning: sugges                                                                                                 t parentheses around ‘&&’ within ‘||’ [-Wparentheses]
     if (data[i] == 0x40 && (data[i + 1] & 0xC0) == 0x00 ||
                         ^
[  6%] Building C object libraries/fc/vendor/easylzma/src/CMakeFiles/easylzma_static.dir/pavl                                                                                                 ov/LzmaLib.c.o
[  7%] Building C object libraries/fc/vendor/easylzma/src/CMakeFiles/easylzma_static.dir/pavl                                                                                                 ov/7zCrc.c.o
[  7%] Building C object libraries/fc/vendor/easylzma/src/CMakeFiles/easylzma_static.dir/pavl                                                                                                 ov/LzmaDec.c.o
[  8%] Building C object libraries/fc/vendor/easylzma/src/CMakeFiles/easylzma_static.dir/pavl                                                                                                 ov/LzFind.c.o
[  8%] Building C object libraries/fc/vendor/easylzma/src/CMakeFiles/easylzma_static.dir/comp                                                                                                 ress.c.o
[  9%] Building C object libraries/fc/vendor/easylzma/src/CMakeFiles/easylzma_static.dir/lzma                                                                                                 _header.c.o
[  9%] Building C object libraries/fc/vendor/easylzma/src/CMakeFiles/easylzma_static.dir/lzma                                                                                                 _c.c.o
[ 10%] Building C object libraries/fc/vendor/easylzma/src/CMakeFiles/easylzma_static.dir/comm                                                                                                 on_internal.c.o
[ 10%] Building C object libraries/fc/vendor/easylzma/src/CMakeFiles/easylzma_static.dir/lzip                                                                                                 _header.c.o
[ 11%] Building C object libraries/fc/vendor/easylzma/src/CMakeFiles/easylzma_static.dir/deco                                                                                                 mpress.c.o
Linking C static library libeasylzma_static.a
[ 11%] Built target easylzma_static
[ 11%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/uint128.cpp.o
[ 12%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/variant.cpp.o
[ 12%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/exception.cpp.o
In file included from /root/bitshares_toolkit/libraries/fc/src/exception.cpp:1:0:
/root/bitshares_toolkit/libraries/fc/include/fc/exception/exception.hpp: In instantiation of                                                                                                  ‘void fc::exception_factory::register_exception() [with T = fc::timeout_exception]’:
/root/bitshares_toolkit/libraries/fc/src/exception.cpp:9:4:   required from here
/root/bitshares_toolkit/libraries/fc/include/fc/exception/exception.hpp:184:17: warning: vari                                                                                                 able ‘itr’ set but not used [-Wunused-but-set-variable]
            auto itr = _registered_exceptions.find( T::code_value );
                 ^
/root/bitshares_toolkit/libraries/fc/include/fc/exception/exception.hpp: In instantiation of                                                                                                  ‘void fc::exception_factory::register_exception() [with T = fc::file_not_found_exception]’:
/root/bitshares_toolkit/libraries/fc/src/exception.cpp:9:4:   required from here
/root/bitshares_toolkit/libraries/fc/include/fc/exception/exception.hpp:184:17: warning: vari                                                                                                 able ‘itr’ set but not used [-Wunused-but-set-variable]
/root/bitshares_toolkit/libraries/fc/include/fc/exception/exception.hpp: In instantiation of                                                                                                  ‘void fc::exception_factory::register_exception() [with T = fc::parse_error_exception]’:
/root/bitshares_toolkit/libraries/fc/src/exception.cpp:9:4:   required from here
/root/bitshares_toolkit/libraries/fc/include/fc/exception/exception.hpp:184:17: warning: vari                                                                                                 able ‘itr’ set but not used [-Wunused-but-set-variable]
/root/bitshares_toolkit/libraries/fc/include/fc/exception/exception.hpp: In instantiation of                                                                                                  ‘void fc::exception_factory::register_exception() [with T = fc::invalid_arg_exception]’:
/root/bitshares_toolkit/libraries/fc/src/exception.cpp:9:4:   required from here
/root/bitshares_toolkit/libraries/fc/include/fc/exception/exception.hpp:184:17: warning: vari                                                                                                 able ‘itr’ set but not used [-Wunused-but-set-variable]
/root/bitshares_toolkit/libraries/fc/include/fc/exception/exception.hpp: In instantiation of                                                                                                  ‘void fc::exception_factory::register_exception() [with T = fc::invalid_operation_exception]’                                                                                                 :
/root/bitshares_toolkit/libraries/fc/src/exception.cpp:9:4:   required from here
/root/bitshares_toolkit/libraries/fc/include/fc/exception/exception.hpp:184:17: warning: vari                                                                                                 able ‘itr’ set but not used [-Wunused-but-set-variable]
/root/bitshares_toolkit/libraries/fc/include/fc/exception/exception.hpp: In instantiation of                                                                                                  ‘void fc::exception_factory::register_exception() [with T = fc::key_not_found_exception]’:
/root/bitshares_toolkit/libraries/fc/src/exception.cpp:9:4:   required from here
/root/bitshares_toolkit/libraries/fc/include/fc/exception/exception.hpp:184:17: warning: vari                                                                                                 able ‘itr’ set but not used [-Wunused-but-set-variable]
/root/bitshares_toolkit/libraries/fc/include/fc/exception/exception.hpp: In instantiation of                                                                                                  ‘void fc::exception_factory::register_exception() [with T = fc::bad_cast_exception]’:
/root/bitshares_toolkit/libraries/fc/src/exception.cpp:9:4:   required from here
/root/bitshares_toolkit/libraries/fc/include/fc/exception/exception.hpp:184:17: warning: vari                                                                                                 able ‘itr’ set but not used [-Wunused-but-set-variable]
/root/bitshares_toolkit/libraries/fc/include/fc/exception/exception.hpp: In instantiation of                                                                                                  ‘void fc::exception_factory::register_exception() [with T = fc::out_of_range_exception]’:
/root/bitshares_toolkit/libraries/fc/src/exception.cpp:9:4:   required from here
/root/bitshares_toolkit/libraries/fc/include/fc/exception/exception.hpp:184:17: warning: vari                                                                                                 able ‘itr’ set but not used [-Wunused-but-set-variable]
/root/bitshares_toolkit/libraries/fc/include/fc/exception/exception.hpp: In instantiation of                                                                                                  ‘void fc::exception_factory::register_exception() [with T = fc::canceled_exception]’:
/root/bitshares_toolkit/libraries/fc/src/exception.cpp:9:4:   required from here
/root/bitshares_toolkit/libraries/fc/include/fc/exception/exception.hpp:184:17: warning: vari                                                                                                 able ‘itr’ set but not used [-Wunused-but-set-variable]
/root/bitshares_toolkit/libraries/fc/include/fc/exception/exception.hpp: In instantiation of                                                                                                  ‘void fc::exception_factory::register_exception() [with T = fc::assert_exception]’:
/root/bitshares_toolkit/libraries/fc/src/exception.cpp:9:4:   required from here
/root/bitshares_toolkit/libraries/fc/include/fc/exception/exception.hpp:184:17: warning: vari                                                                                                 able ‘itr’ set but not used [-Wunused-but-set-variable]
/root/bitshares_toolkit/libraries/fc/include/fc/exception/exception.hpp: In instantiation of                                                                                                  ‘void fc::exception_factory::register_exception() [with T = fc::eof_exception]’:
/root/bitshares_toolkit/libraries/fc/src/exception.cpp:9:4:   required from here
/root/bitshares_toolkit/libraries/fc/include/fc/exception/exception.hpp:184:17: warning: vari                                                                                                 able ‘itr’ set but not used [-Wunused-but-set-variable]
[ 13%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/variant_object.cpp.o
[ 13%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/thread/thread.cpp.o
[ 14%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/thread/future.cpp.o
[ 14%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/thread/task.cpp.o
[ 15%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/thread/spin_lock.cpp.o
[ 15%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/thread/spin_yield_lock.cpp.o
[ 16%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/thread/mutex.cpp.o
[ 16%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/asio.cpp.o
[ 17%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/string.cpp.o
[ 17%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/shared_ptr.cpp.o
[ 18%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/time.cpp.o
[ 19%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/utf8.cpp.o
[ 19%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/io/iostream.cpp.o
[ 20%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/io/datastream.cpp.o
[ 20%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/io/buffered_iostream.cpp.o
[ 21%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/io/fstream.cpp.o
[ 21%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/io/sstream.cpp.o
[ 22%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/io/json.cpp.o
[ 22%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/io/varint.cpp.o
[ 23%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/io/console.cpp.o
[ 23%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/filesystem.cpp.o
[ 24%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/interprocess/process.cpp.o
c++: internal compiler error: Killed (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-4.8/README.Bugs> for instructions.
make[2]: *** [libraries/fc/CMakeFiles/fc.dir/src/interprocess/process.cpp.o] Error 4
make[1]: *** [libraries/fc/CMakeFiles/fc.dir/all] Error 2
make: *** [all] Error 2


Title: Re: Initial delegates, let's get ready!
Post by: bitcoinerS on June 08, 2014, 04:14:41 am
3) Generate up to five keys. Use the utility at bitshares_toolkit/programs/utils/bts_create_key

Share with us the *public key* (not address)
Keep the *private key WIF format* (not the plain private key - actually keep both, WIF is just what you import)


After generating keys do I need to import them into bts client?
Title: Re: Initial delegates, let's get ready!
Post by: bitcoinerS on June 08, 2014, 04:23:23 am
tried importing generated key. Getting an error.

Code: [Select]
default (unlocked) >>> wallet_import_private_key 5KP7Qa3kcnBfWa3uJqo6S6j1jqfpVz8FVE5CJsirHEZRcYDDtfr "delegate-1"
10
is_valid_account( account_name ):
    {}
    th_a  wallet.cpp:784 import_private_key

    {"account_name":"delegate-1"}
    th_a  wallet.cpp:811 import_private_key

    {"account_name":"delegate-1"}
    th_a  wallet.cpp:830 import_wif_private_key

    {}
    th_a  common_api_client.cpp:202 wallet_import_private_key

    {"command":"wallet_import_private_key"}
    th_a  cli.cpp:574 execute_command
Title: Re: Initial delegates, let's get ready!
Post by: toast on June 08, 2014, 04:25:34 am
You can import them but it won't do anything because you aren't a delegate in this test network.

For "wallet_import_private_key", the second argument needs to be the name of an account in your wallet ("wallet_create_account name")
(OR the key needs to be for a name that is registered in the blockchain, hence the instructions for puppies and emski)
Title: Re: Initial delegates, let's get ready!
Post by: Xeldal on June 08, 2014, 04:29:43 am
I get to 24% with Ubuntu 14.04 x64 and 80% on x32

Code: [Select]
root@xt:~/bitshares_toolkit# make

... (30000 word limit)

[ 24%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/interprocess/process.cpp.o
[ 24%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/interprocess/signals.cpp.o
[ 25%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/interprocess/file_mapping.cpp.o
[ 25%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/interprocess/mmap_struct.cpp.o
[ 26%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/rpc/json_connection.cpp.o
[ 26%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/log/log_message.cpp.o
[ 27%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/log/logger.cpp.o
[ 27%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/log/appender.cpp.o
[ 28%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/log/console_appender.cpp.o
[ 28%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/log/file_appender.cpp.o
[ 29%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/log/logger_config.cpp.o
[ 29%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/crypto/openssl.cpp.o
[ 30%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/crypto/aes.cpp.o
/root/bitshares_toolkit/libraries/fc/src/crypto/aes.cpp: In constructor ‘fc::aes_encoder::aes_encoder()’:
/root/bitshares_toolkit/libraries/fc/src/crypto/aes.cpp:20:14: warning: unused variable ‘init’ [-Wunused-variable]
   static int init = init_openssl();
              ^
In file included from /root/bitshares_toolkit/libraries/fc/src/crypto/aes.cpp:3:0:
/root/bitshares_toolkit/libraries/fc/src/crypto/aes.cpp: In member function ‘uint32_t fc::aes_encoder::encode(const char*, uint32_t, char*)’:
/root/bitshares_toolkit/libraries/fc/src/crypto/aes.cpp:61:34: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
     FC_ASSERT( ciphertext_len == plaintext_len, "", ("ciphertext_len",ciphertext_len)("plaintext_len",plaintext_len) );
                                  ^
/root/bitshares_toolkit/libraries/fc/include/fc/exception/exception.hpp:273:30: note: in definition of macro ‘FC_EXPAND_MACRO’
 #define FC_EXPAND_MACRO( x ) x
                              ^
/root/bitshares_toolkit/libraries/fc/src/crypto/aes.cpp:61:5: note: in expansion of macro ‘FC_ASSERT’
     FC_ASSERT( ciphertext_len == plaintext_len, "", ("ciphertext_len",ciphertext_len)("plaintext_len",plaintext_len) );
     ^
/root/bitshares_toolkit/libraries/fc/src/crypto/aes.cpp: In constructor ‘fc::aes_decoder::aes_decoder()’:
/root/bitshares_toolkit/libraries/fc/src/crypto/aes.cpp:88:14: warning: unused variable ‘init’ [-Wunused-variable]
   static int init = init_openssl();
              ^
In file included from /root/bitshares_toolkit/libraries/fc/src/crypto/aes.cpp:3:0:
/root/bitshares_toolkit/libraries/fc/src/crypto/aes.cpp: In member function ‘uint32_t fc::aes_decoder::decode(const char*, uint32_t, char*)’:
/root/bitshares_toolkit/libraries/fc/src/crypto/aes.cpp:128:33: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
     FC_ASSERT( ciphertxt_len == plaintext_len, "", ("ciphertxt_len",ciphertxt_len)("plaintext_len",plaintext_len) );
                                 ^
/root/bitshares_toolkit/libraries/fc/include/fc/exception/exception.hpp:273:30: note: in definition of macro ‘FC_EXPAND_MACRO’
 #define FC_EXPAND_MACRO( x ) x
                              ^
/root/bitshares_toolkit/libraries/fc/src/crypto/aes.cpp:128:5: note: in expansion of macro ‘FC_ASSERT’
     FC_ASSERT( ciphertxt_len == plaintext_len, "", ("ciphertxt_len",ciphertxt_len)("plaintext_len",plaintext_len) );
     ^
/root/bitshares_toolkit/libraries/fc/src/crypto/aes.cpp: In function ‘std::vector<char> fc::aes_encrypt(const fc::sha512&, const std::vector<char>&)’:
/root/bitshares_toolkit/libraries/fc/src/crypto/aes.cpp:313:47: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
     FC_ASSERT( cipher_len <= cipher_text.size() );
                                               ^
/root/bitshares_toolkit/libraries/fc/include/fc/exception/exception.hpp:273:30: note: in definition of macro ‘FC_EXPAND_MACRO’
 #define FC_EXPAND_MACRO( x ) x
                              ^
/root/bitshares_toolkit/libraries/fc/src/crypto/aes.cpp:313:5: note: in expansion of macro ‘FC_ASSERT’
     FC_ASSERT( cipher_len <= cipher_text.size() );
     ^
[ 30%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/crypto/crc.cpp.o
[ 31%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/crypto/city.cpp.o
[ 31%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/crypto/base32.cpp.o
[ 32%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/crypto/base36.cpp.o
[ 32%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/crypto/base58.cpp.o
[ 33%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/crypto/base64.cpp.o
[ 34%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/crypto/bigint.cpp.o
[ 34%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/crypto/hex.cpp.o
[ 35%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/crypto/sha1.cpp.o
[ 35%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/crypto/ripemd160.cpp.o
[ 36%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/crypto/sha256.cpp.o
[ 36%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/crypto/sha224.cpp.o
[ 37%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/crypto/sha512.cpp.o
[ 37%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/crypto/dh.cpp.o
[ 38%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/crypto/blowfish.cpp.o
[ 38%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/crypto/elliptic.cpp.o
/root/bitshares_toolkit/libraries/fc/src/crypto/elliptic.cpp: In constructor ‘fc::ecc::detail::public_key_impl::public_key_impl()’:
/root/bitshares_toolkit/libraries/fc/src/crypto/elliptic.cpp:21:22: warning: unused variable ‘init’ [-Wunused-variable]
           static int init = init_openssl();
                      ^
/root/bitshares_toolkit/libraries/fc/src/crypto/elliptic.cpp: In constructor ‘fc::ecc::detail::private_key_impl::private_key_impl()’:
/root/bitshares_toolkit/libraries/fc/src/crypto/elliptic.cpp:43:22: warning: unused variable ‘init’ [-Wunused-variable]
           static int init = init_openssl();
                      ^
[ 39%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/crypto/rand.cpp.o
/root/bitshares_toolkit/libraries/fc/src/crypto/rand.cpp: In function ‘void fc::rand_bytes(char*, int)’:
/root/bitshares_toolkit/libraries/fc/src/crypto/rand.cpp:11:14: warning: unused variable ‘init’ [-Wunused-variable]
   static int init = init_openssl();
              ^
/root/bitshares_toolkit/libraries/fc/src/crypto/rand.cpp: In function ‘void fc::rand_pseudo_bytes(char*, int)’:
/root/bitshares_toolkit/libraries/fc/src/crypto/rand.cpp:20:14: warning: unused variable ‘init’ [-Wunused-variable]
   static int init = init_openssl();
              ^
[ 39%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/crypto/salsa20.cpp.o
[ 40%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/crypto/scrypt.cpp.o
[ 40%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/network/tcp_socket.cpp.o
[ 41%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/network/udp_socket.cpp.o
[ 41%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/network/http/http_connection.cpp.o
[ 42%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/network/http/http_server.cpp.o
[ 42%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/network/ip.cpp.o
[ 43%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/network/rate_limiting.cpp.o
[ 43%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/network/resolve.cpp.o
[ 44%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/network/url.cpp.o
[ 44%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/compress/smaz.cpp.o
[ 45%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/compress/lzma.cpp.o
[ 45%] Building C object libraries/fc/CMakeFiles/fc.dir/vendor/cyoencode-1.0.2/src/CyoDecode.c.o
cc1: warning: command line option ‘-std=c++11’ is valid for C++/ObjC++ but not for C [enabled by default]
[ 46%] Building C object libraries/fc/CMakeFiles/fc.dir/vendor/cyoencode-1.0.2/src/CyoEncode.c.o
cc1: warning: command line option ‘-std=c++11’ is valid for C++/ObjC++ but not for C [enabled by default]
[ 46%] Building C object libraries/fc/CMakeFiles/fc.dir/vendor/salsa20/salsa20.s.o
[ 47%] Building CXX object libraries/fc/CMakeFiles/fc.dir/git_revision.cpp.o
Linking CXX static library libfc.a
Copying OpenSSL/ssl/openssl.cnf into target directory.
[ 47%] Built target fc
Scanning dependencies of target leveldb
[ 47%] Building CXX object vendor/leveldb-1.12.0/CMakeFiles/leveldb.dir/db/builder.cc.o
[ 48%] Building CXX object vendor/leveldb-1.12.0/CMakeFiles/leveldb.dir/db/c.cc.o
[ 48%] Building CXX object vendor/leveldb-1.12.0/CMakeFiles/leveldb.dir/db/db_impl.cc.o
[ 49%] Building CXX object vendor/leveldb-1.12.0/CMakeFiles/leveldb.dir/db/db_iter.cc.o
[ 49%] Building CXX object vendor/leveldb-1.12.0/CMakeFiles/leveldb.dir/db/dbformat.cc.o
[ 50%] Building CXX object vendor/leveldb-1.12.0/CMakeFiles/leveldb.dir/db/filename.cc.o
[ 50%] Building CXX object vendor/leveldb-1.12.0/CMakeFiles/leveldb.dir/db/log_reader.cc.o
[ 51%] Building CXX object vendor/leveldb-1.12.0/CMakeFiles/leveldb.dir/db/log_writer.cc.o
[ 51%] Building CXX object vendor/leveldb-1.12.0/CMakeFiles/leveldb.dir/db/memtable.cc.o
[ 52%] Building CXX object vendor/leveldb-1.12.0/CMakeFiles/leveldb.dir/db/repair.cc.o
[ 52%] Building CXX object vendor/leveldb-1.12.0/CMakeFiles/leveldb.dir/db/table_cache.cc.o
[ 53%] Building CXX object vendor/leveldb-1.12.0/CMakeFiles/leveldb.dir/db/version_edit.cc.o
[ 53%] Building CXX object vendor/leveldb-1.12.0/CMakeFiles/leveldb.dir/db/version_set.cc.o
[ 54%] Building CXX object vendor/leveldb-1.12.0/CMakeFiles/leveldb.dir/db/write_batch.cc.o
[ 54%] Building CXX object vendor/leveldb-1.12.0/CMakeFiles/leveldb.dir/port/port_posix.cc.o
[ 55%] Building CXX object vendor/leveldb-1.12.0/CMakeFiles/leveldb.dir/helpers/memenv/memenv.cc.o
[ 55%] Building CXX object vendor/leveldb-1.12.0/CMakeFiles/leveldb.dir/util/arena.cc.o
[ 56%] Building CXX object vendor/leveldb-1.12.0/CMakeFiles/leveldb.dir/util/bloom.cc.o
/root/bitshares_toolkit/vendor/leveldb-1.12.0/util/bloom.cc: In member function ‘virtual void leveldb::{anonymous}::BloomFilterPolicy::CreateFilter(const leveldb::Slice*, int, std::string*) const’:
/root/bitshares_toolkit/vendor/leveldb-1.12.0/util/bloom.cc:50:28: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
     for (size_t i = 0; i < n; i++) {
                            ^
[ 56%] Building CXX object vendor/leveldb-1.12.0/CMakeFiles/leveldb.dir/util/cache.cc.o
[ 57%] Building CXX object vendor/leveldb-1.12.0/CMakeFiles/leveldb.dir/util/coding.cc.o
[ 57%] Building CXX object vendor/leveldb-1.12.0/CMakeFiles/leveldb.dir/util/comparator.cc.o
[ 58%] Building CXX object vendor/leveldb-1.12.0/CMakeFiles/leveldb.dir/util/crc32c.cc.o
[ 58%] Building CXX object vendor/leveldb-1.12.0/CMakeFiles/leveldb.dir/util/env.cc.o
[ 59%] Building CXX object vendor/leveldb-1.12.0/CMakeFiles/leveldb.dir/util/env_posix.cc.o
[ 59%] Building CXX object vendor/leveldb-1.12.0/CMakeFiles/leveldb.dir/util/filter_policy.cc.o
[ 60%] Building CXX object vendor/leveldb-1.12.0/CMakeFiles/leveldb.dir/util/hash.cc.o
[ 61%] Building CXX object vendor/leveldb-1.12.0/CMakeFiles/leveldb.dir/util/histogram.cc.o
[ 61%] Building CXX object vendor/leveldb-1.12.0/CMakeFiles/leveldb.dir/util/logging.cc.o
/root/bitshares_toolkit/vendor/leveldb-1.12.0/util/logging.cc: In function ‘bool leveldb::ConsumeDecimalNumber(leveldb::Slice*, uint64_t*)’:
/root/bitshares_toolkit/vendor/leveldb-1.12.0/util/logging.cc:67:53: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
           (v == kMaxUint64/10 && delta > kMaxUint64%10)) {
                                                     ^
[ 62%] Building CXX object vendor/leveldb-1.12.0/CMakeFiles/leveldb.dir/util/options.cc.o
[ 62%] Building CXX object vendor/leveldb-1.12.0/CMakeFiles/leveldb.dir/util/status.cc.o
[ 63%] Building CXX object vendor/leveldb-1.12.0/CMakeFiles/leveldb.dir/table/block.cc.o
[ 63%] Building CXX object vendor/leveldb-1.12.0/CMakeFiles/leveldb.dir/table/block_builder.cc.o
[ 64%] Building CXX object vendor/leveldb-1.12.0/CMakeFiles/leveldb.dir/table/filter_block.cc.o
/root/bitshares_toolkit/vendor/leveldb-1.12.0/table/filter_block.cc: In member function ‘bool leveldb::FilterBlockReader::KeyMayMatch(uint64_t, const leveldb::Slice&)’:
/root/bitshares_toolkit/vendor/leveldb-1.12.0/table/filter_block.cc:100:52: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
     if (start <= limit && limit <= (offset_ - data_)) {
                                                    ^
[ 64%] Building CXX object vendor/leveldb-1.12.0/CMakeFiles/leveldb.dir/table/format.cc.o
[ 65%] Building CXX object vendor/leveldb-1.12.0/CMakeFiles/leveldb.dir/table/iterator.cc.o
[ 65%] Building CXX object vendor/leveldb-1.12.0/CMakeFiles/leveldb.dir/table/merger.cc.o
[ 66%] Building CXX object vendor/leveldb-1.12.0/CMakeFiles/leveldb.dir/table/table.cc.o
[ 66%] Building CXX object vendor/leveldb-1.12.0/CMakeFiles/leveldb.dir/table/table_builder.cc.o
[ 67%] Building CXX object vendor/leveldb-1.12.0/CMakeFiles/leveldb.dir/table/two_level_iterator.cc.o
Linking CXX static library libleveldb.a
[ 67%] Built target leveldb
Scanning dependencies of target bts_db
[ 68%] Building CXX object libraries/db/CMakeFiles/bts_db.dir/upgrade_leveldb.cpp.o
In file included from /root/bitshares_toolkit/libraries/db/include/bts/db/exception.hpp:2:0,
                 from /root/bitshares_toolkit/libraries/db/upgrade_leveldb.cpp:1:
/root/bitshares_toolkit/libraries/fc/include/fc/exception/exception.hpp: In instantiation of ‘void fc::exception_factory::register_exception() [with T = bts::db::db_exception]’:
/root/bitshares_toolkit/libraries/db/upgrade_leveldb.cpp:9:5:   required from here
/root/bitshares_toolkit/libraries/fc/include/fc/exception/exception.hpp:184:17: warning: variable ‘itr’ set but not used [-Wunused-but-set-variable]
            auto itr = _registered_exceptions.find( T::code_value );
                 ^
/root/bitshares_toolkit/libraries/fc/include/fc/exception/exception.hpp: In instantiation of ‘void fc::exception_factory::register_exception() [with T = bts::db::db_in_use_exception]’:
/root/bitshares_toolkit/libraries/db/upgrade_leveldb.cpp:9:5:   required from here
/root/bitshares_toolkit/libraries/fc/include/fc/exception/exception.hpp:184:17: warning: variable ‘itr’ set but not used [-Wunused-but-set-variable]
Linking CXX static library libbts_db.a
[ 68%] Built target bts_db
Scanning dependencies of target bts_utilities
[ 69%] Building CXX object libraries/utilities/CMakeFiles/bts_utilities.dir/key_conversion.cpp.o
[ 69%] Building CXX object libraries/utilities/CMakeFiles/bts_utilities.dir/string_escape.cpp.o
[ 70%] Building CXX object libraries/utilities/CMakeFiles/bts_utilities.dir/git_revision.cpp.o
Linking CXX static library libbts_utilities.a
[ 70%] Built target bts_utilities
Scanning dependencies of target bts_api_generator
[ 71%] Building CXX object libraries/api/CMakeFiles/bts_api_generator.dir/bts_api_generator.cpp.o
Linking CXX executable bts_api_generator
[ 71%] Built target bts_api_generator
[ 72%] Generating include/bts/api/common_api.hpp, ../rpc_stubs/common_api_rpc_server.cpp, ../rpc_stubs/common_api_rpc_client.cpp, ../rpc_stubs/common_api_client.cpp, ../rpc_stubs/include/bts/rpc_stubs/common_api_rpc_server.hpp, ../rpc_stubs/include/bts/rpc_stubs/common_api_rpc_client.hpp, ../rpc_stubs/include/bts/rpc_stubs/common_api_client.hpp, ../rpc_stubs/include/bts/rpc_stubs/common_api_overrides.ipp
Scanning dependencies of target bts_api
[ 72%] Building CXX object libraries/api/CMakeFiles/bts_api.dir/conversion_functions.cpp.o
Linking CXX static library libbts_api.a
[ 72%] Built target bts_api
Scanning dependencies of target bts_blockchain
[ 72%] Building CXX object libraries/blockchain/CMakeFiles/bts_blockchain.dir/time.cpp.o
[ 73%] Building CXX object libraries/blockchain/CMakeFiles/bts_blockchain.dir/extended_address.cpp.o
[ 73%] Building CXX object libraries/blockchain/CMakeFiles/bts_blockchain.dir/address.cpp.o
[ 74%] Building CXX object libraries/blockchain/CMakeFiles/bts_blockchain.dir/pts_address.cpp.o
[ 74%] Building CXX object libraries/blockchain/CMakeFiles/bts_blockchain.dir/asset.cpp.o
[ 75%] Building CXX object libraries/blockchain/CMakeFiles/bts_blockchain.dir/types.cpp.o
[ 75%] Building CXX object libraries/blockchain/CMakeFiles/bts_blockchain.dir/operations.cpp.o
[ 76%] Building CXX object libraries/blockchain/CMakeFiles/bts_blockchain.dir/withdraw_types.cpp.o
[ 76%] Building CXX object libraries/blockchain/CMakeFiles/bts_blockchain.dir/pending_chain_state.cpp.o
[ 77%] Building CXX object libraries/blockchain/CMakeFiles/bts_blockchain.dir/transaction.cpp.o
[ 77%] Building CXX object libraries/blockchain/CMakeFiles/bts_blockchain.dir/chain_interface.cpp.o
[ 78%] Building CXX object libraries/blockchain/CMakeFiles/bts_blockchain.dir/block.cpp.o
[ 78%] Building CXX object libraries/blockchain/CMakeFiles/bts_blockchain.dir/chain_database.cpp.o
In file included from /root/bitshares_toolkit/libraries/blockchain/include/bts/blockchain/exceptions.hpp:2:0,
                 from /root/bitshares_toolkit/libraries/blockchain/chain_database.cpp:1:
/root/bitshares_toolkit/libraries/fc/include/fc/exception/exception.hpp: In instantiation of ‘void fc::exception_factory::register_exception() [with T = bts::blockchain::invalid_pts_address]’:
/root/bitshares_toolkit/libraries/blockchain/chain_database.cpp:94:4:   required from here
/root/bitshares_toolkit/libraries/fc/include/fc/exception/exception.hpp:184:17: warning: variable ‘itr’ set but not used [-Wunused-but-set-variable]
            auto itr = _registered_exceptions.find( T::code_value );
                 ^
/root/bitshares_toolkit/libraries/fc/include/fc/exception/exception.hpp: In instantiation of ‘void fc::exception_factory::register_exception() [with T = bts::blockchain::addition_overflow]’:
/root/bitshares_toolkit/libraries/blockchain/chain_database.cpp:94:4:   required from here
/root/bitshares_toolkit/libraries/fc/include/fc/exception/exception.hpp:184:17: warning: variable ‘itr’ set but not used [-Wunused-but-set-variable]
/root/bitshares_toolkit/libraries/fc/include/fc/exception/exception.hpp: In instantiation of ‘void fc::exception_factory::register_exception() [with T = bts::blockchain::addition_underthrow]’:
/root/bitshares_toolkit/libraries/blockchain/chain_database.cpp:94:4:   required from here
/root/bitshares_toolkit/libraries/fc/include/fc/exception/exception.hpp:184:17: warning: variable ‘itr’ set but not used [-Wunused-but-set-variable]
/root/bitshares_toolkit/libraries/fc/include/fc/exception/exception.hpp: In instantiation of ‘void fc::exception_factory::register_exception() [with T = bts::blockchain::asset_type_mismatch]’:
/root/bitshares_toolkit/libraries/blockchain/chain_database.cpp:94:4:   required from here
/root/bitshares_toolkit/libraries/fc/include/fc/exception/exception.hpp:184:17: warning: variable ‘itr’ set but not used [-Wunused-but-set-variable]
[ 79%] Building CXX object libraries/blockchain/CMakeFiles/bts_blockchain.dir/fire_operation.cpp.o
[ 79%] Building CXX object libraries/blockchain/CMakeFiles/bts_blockchain.dir/account_record.cpp.o
Linking CXX static library libbts_blockchain.a
[ 79%] Built target bts_blockchain
Scanning dependencies of target bitcoin
[ 79%] Building CXX object libraries/bitcoin/CMakeFiles/bitcoin.dir/armory.cpp.o
[ 80%] Building CXX object libraries/bitcoin/CMakeFiles/bitcoin.dir/bitcoin.cpp.o
[ 80%] Building CXX object libraries/bitcoin/CMakeFiles/bitcoin.dir/electrum.cpp.o
c++: internal compiler error: Killed (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-4.8/README.Bugs> for instructions.
make[2]: *** [libraries/bitcoin/CMakeFiles/bitcoin.dir/electrum.cpp.o] Error 4
make[1]: *** [libraries/bitcoin/CMakeFiles/bitcoin.dir/all] Error 2
make: *** [all] Error 2
root@xt:~/bitshares_toolkit#
Title: Re: Initial delegates, let's get ready!
Post by: toast on June 08, 2014, 04:41:06 am
I get to 24% with Ubuntu 14.04 x64 and 80% on x32

Code: [Select]
root@xt:~/bitshares_toolkit# make

... (30000 word limit)

[ 24%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/interprocess/process.cpp.o
[ 24%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/interprocess/signals.cpp.o
[ 25%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/interprocess/file_mapping.cpp.o
[ 25%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/interprocess/mmap_struct.cpp.o
[ 26%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/rpc/json_connection.cpp.o
[ 26%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/log/log_message.cpp.o
[ 27%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/log/logger.cpp.o
[ 27%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/log/appender.cpp.o
[ 28%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/log/console_appender.cpp.o
[ 28%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/log/file_appender.cpp.o
[ 29%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/log/logger_config.cpp.o
[ 29%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/crypto/openssl.cpp.o
[ 30%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/crypto/aes.cpp.o
/root/bitshares_toolkit/libraries/fc/src/crypto/aes.cpp: In constructor ‘fc::aes_encoder::aes_encoder()’:
/root/bitshares_toolkit/libraries/fc/src/crypto/aes.cpp:20:14: warning: unused variable ‘init’ [-Wunused-variable]
   static int init = init_openssl();
              ^
In file included from /root/bitshares_toolkit/libraries/fc/src/crypto/aes.cpp:3:0:
/root/bitshares_toolkit/libraries/fc/src/crypto/aes.cpp: In member function ‘uint32_t fc::aes_encoder::encode(const char*, uint32_t, char*)’:
/root/bitshares_toolkit/libraries/fc/src/crypto/aes.cpp:61:34: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
     FC_ASSERT( ciphertext_len == plaintext_len, "", ("ciphertext_len",ciphertext_len)("plaintext_len",plaintext_len) );
                                  ^
/root/bitshares_toolkit/libraries/fc/include/fc/exception/exception.hpp:273:30: note: in definition of macro ‘FC_EXPAND_MACRO’
 #define FC_EXPAND_MACRO( x ) x
                              ^
/root/bitshares_toolkit/libraries/fc/src/crypto/aes.cpp:61:5: note: in expansion of macro ‘FC_ASSERT’
     FC_ASSERT( ciphertext_len == plaintext_len, "", ("ciphertext_len",ciphertext_len)("plaintext_len",plaintext_len) );
     ^
/root/bitshares_toolkit/libraries/fc/src/crypto/aes.cpp: In constructor ‘fc::aes_decoder::aes_decoder()’:
/root/bitshares_toolkit/libraries/fc/src/crypto/aes.cpp:88:14: warning: unused variable ‘init’ [-Wunused-variable]
   static int init = init_openssl();
              ^
In file included from /root/bitshares_toolkit/libraries/fc/src/crypto/aes.cpp:3:0:
/root/bitshares_toolkit/libraries/fc/src/crypto/aes.cpp: In member function ‘uint32_t fc::aes_decoder::decode(const char*, uint32_t, char*)’:
/root/bitshares_toolkit/libraries/fc/src/crypto/aes.cpp:128:33: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
     FC_ASSERT( ciphertxt_len == plaintext_len, "", ("ciphertxt_len",ciphertxt_len)("plaintext_len",plaintext_len) );
                                 ^
/root/bitshares_toolkit/libraries/fc/include/fc/exception/exception.hpp:273:30: note: in definition of macro ‘FC_EXPAND_MACRO’
 #define FC_EXPAND_MACRO( x ) x
                              ^
/root/bitshares_toolkit/libraries/fc/src/crypto/aes.cpp:128:5: note: in expansion of macro ‘FC_ASSERT’
     FC_ASSERT( ciphertxt_len == plaintext_len, "", ("ciphertxt_len",ciphertxt_len)("plaintext_len",plaintext_len) );
     ^
/root/bitshares_toolkit/libraries/fc/src/crypto/aes.cpp: In function ‘std::vector<char> fc::aes_encrypt(const fc::sha512&, const std::vector<char>&)’:
/root/bitshares_toolkit/libraries/fc/src/crypto/aes.cpp:313:47: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
     FC_ASSERT( cipher_len <= cipher_text.size() );
                                               ^
/root/bitshares_toolkit/libraries/fc/include/fc/exception/exception.hpp:273:30: note: in definition of macro ‘FC_EXPAND_MACRO’
 #define FC_EXPAND_MACRO( x ) x
                              ^
/root/bitshares_toolkit/libraries/fc/src/crypto/aes.cpp:313:5: note: in expansion of macro ‘FC_ASSERT’
     FC_ASSERT( cipher_len <= cipher_text.size() );
     ^
[ 30%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/crypto/crc.cpp.o
[ 31%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/crypto/city.cpp.o
[ 31%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/crypto/base32.cpp.o
[ 32%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/crypto/base36.cpp.o
[ 32%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/crypto/base58.cpp.o
[ 33%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/crypto/base64.cpp.o
[ 34%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/crypto/bigint.cpp.o
[ 34%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/crypto/hex.cpp.o
[ 35%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/crypto/sha1.cpp.o
[ 35%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/crypto/ripemd160.cpp.o
[ 36%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/crypto/sha256.cpp.o
[ 36%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/crypto/sha224.cpp.o
[ 37%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/crypto/sha512.cpp.o
[ 37%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/crypto/dh.cpp.o
[ 38%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/crypto/blowfish.cpp.o
[ 38%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/crypto/elliptic.cpp.o
/root/bitshares_toolkit/libraries/fc/src/crypto/elliptic.cpp: In constructor ‘fc::ecc::detail::public_key_impl::public_key_impl()’:
/root/bitshares_toolkit/libraries/fc/src/crypto/elliptic.cpp:21:22: warning: unused variable ‘init’ [-Wunused-variable]
           static int init = init_openssl();
                      ^
/root/bitshares_toolkit/libraries/fc/src/crypto/elliptic.cpp: In constructor ‘fc::ecc::detail::private_key_impl::private_key_impl()’:
/root/bitshares_toolkit/libraries/fc/src/crypto/elliptic.cpp:43:22: warning: unused variable ‘init’ [-Wunused-variable]
           static int init = init_openssl();
                      ^
[ 39%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/crypto/rand.cpp.o
/root/bitshares_toolkit/libraries/fc/src/crypto/rand.cpp: In function ‘void fc::rand_bytes(char*, int)’:
/root/bitshares_toolkit/libraries/fc/src/crypto/rand.cpp:11:14: warning: unused variable ‘init’ [-Wunused-variable]
   static int init = init_openssl();
              ^
/root/bitshares_toolkit/libraries/fc/src/crypto/rand.cpp: In function ‘void fc::rand_pseudo_bytes(char*, int)’:
/root/bitshares_toolkit/libraries/fc/src/crypto/rand.cpp:20:14: warning: unused variable ‘init’ [-Wunused-variable]
   static int init = init_openssl();
              ^
[ 39%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/crypto/salsa20.cpp.o
[ 40%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/crypto/scrypt.cpp.o
[ 40%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/network/tcp_socket.cpp.o
[ 41%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/network/udp_socket.cpp.o
[ 41%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/network/http/http_connection.cpp.o
[ 42%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/network/http/http_server.cpp.o
[ 42%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/network/ip.cpp.o
[ 43%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/network/rate_limiting.cpp.o
[ 43%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/network/resolve.cpp.o
[ 44%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/network/url.cpp.o
[ 44%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/compress/smaz.cpp.o
[ 45%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/compress/lzma.cpp.o
[ 45%] Building C object libraries/fc/CMakeFiles/fc.dir/vendor/cyoencode-1.0.2/src/CyoDecode.c.o
cc1: warning: command line option ‘-std=c++11’ is valid for C++/ObjC++ but not for C [enabled by default]
[ 46%] Building C object libraries/fc/CMakeFiles/fc.dir/vendor/cyoencode-1.0.2/src/CyoEncode.c.o
cc1: warning: command line option ‘-std=c++11’ is valid for C++/ObjC++ but not for C [enabled by default]
[ 46%] Building C object libraries/fc/CMakeFiles/fc.dir/vendor/salsa20/salsa20.s.o
[ 47%] Building CXX object libraries/fc/CMakeFiles/fc.dir/git_revision.cpp.o
Linking CXX static library libfc.a
Copying OpenSSL/ssl/openssl.cnf into target directory.
[ 47%] Built target fc
Scanning dependencies of target leveldb
[ 47%] Building CXX object vendor/leveldb-1.12.0/CMakeFiles/leveldb.dir/db/builder.cc.o
[ 48%] Building CXX object vendor/leveldb-1.12.0/CMakeFiles/leveldb.dir/db/c.cc.o
[ 48%] Building CXX object vendor/leveldb-1.12.0/CMakeFiles/leveldb.dir/db/db_impl.cc.o
[ 49%] Building CXX object vendor/leveldb-1.12.0/CMakeFiles/leveldb.dir/db/db_iter.cc.o
[ 49%] Building CXX object vendor/leveldb-1.12.0/CMakeFiles/leveldb.dir/db/dbformat.cc.o
[ 50%] Building CXX object vendor/leveldb-1.12.0/CMakeFiles/leveldb.dir/db/filename.cc.o
[ 50%] Building CXX object vendor/leveldb-1.12.0/CMakeFiles/leveldb.dir/db/log_reader.cc.o
[ 51%] Building CXX object vendor/leveldb-1.12.0/CMakeFiles/leveldb.dir/db/log_writer.cc.o
[ 51%] Building CXX object vendor/leveldb-1.12.0/CMakeFiles/leveldb.dir/db/memtable.cc.o
[ 52%] Building CXX object vendor/leveldb-1.12.0/CMakeFiles/leveldb.dir/db/repair.cc.o
[ 52%] Building CXX object vendor/leveldb-1.12.0/CMakeFiles/leveldb.dir/db/table_cache.cc.o
[ 53%] Building CXX object vendor/leveldb-1.12.0/CMakeFiles/leveldb.dir/db/version_edit.cc.o
[ 53%] Building CXX object vendor/leveldb-1.12.0/CMakeFiles/leveldb.dir/db/version_set.cc.o
[ 54%] Building CXX object vendor/leveldb-1.12.0/CMakeFiles/leveldb.dir/db/write_batch.cc.o
[ 54%] Building CXX object vendor/leveldb-1.12.0/CMakeFiles/leveldb.dir/port/port_posix.cc.o
[ 55%] Building CXX object vendor/leveldb-1.12.0/CMakeFiles/leveldb.dir/helpers/memenv/memenv.cc.o
[ 55%] Building CXX object vendor/leveldb-1.12.0/CMakeFiles/leveldb.dir/util/arena.cc.o
[ 56%] Building CXX object vendor/leveldb-1.12.0/CMakeFiles/leveldb.dir/util/bloom.cc.o
/root/bitshares_toolkit/vendor/leveldb-1.12.0/util/bloom.cc: In member function ‘virtual void leveldb::{anonymous}::BloomFilterPolicy::CreateFilter(const leveldb::Slice*, int, std::string*) const’:
/root/bitshares_toolkit/vendor/leveldb-1.12.0/util/bloom.cc:50:28: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
     for (size_t i = 0; i < n; i++) {
                            ^
[ 56%] Building CXX object vendor/leveldb-1.12.0/CMakeFiles/leveldb.dir/util/cache.cc.o
[ 57%] Building CXX object vendor/leveldb-1.12.0/CMakeFiles/leveldb.dir/util/coding.cc.o
[ 57%] Building CXX object vendor/leveldb-1.12.0/CMakeFiles/leveldb.dir/util/comparator.cc.o
[ 58%] Building CXX object vendor/leveldb-1.12.0/CMakeFiles/leveldb.dir/util/crc32c.cc.o
[ 58%] Building CXX object vendor/leveldb-1.12.0/CMakeFiles/leveldb.dir/util/env.cc.o
[ 59%] Building CXX object vendor/leveldb-1.12.0/CMakeFiles/leveldb.dir/util/env_posix.cc.o
[ 59%] Building CXX object vendor/leveldb-1.12.0/CMakeFiles/leveldb.dir/util/filter_policy.cc.o
[ 60%] Building CXX object vendor/leveldb-1.12.0/CMakeFiles/leveldb.dir/util/hash.cc.o
[ 61%] Building CXX object vendor/leveldb-1.12.0/CMakeFiles/leveldb.dir/util/histogram.cc.o
[ 61%] Building CXX object vendor/leveldb-1.12.0/CMakeFiles/leveldb.dir/util/logging.cc.o
/root/bitshares_toolkit/vendor/leveldb-1.12.0/util/logging.cc: In function ‘bool leveldb::ConsumeDecimalNumber(leveldb::Slice*, uint64_t*)’:
/root/bitshares_toolkit/vendor/leveldb-1.12.0/util/logging.cc:67:53: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
           (v == kMaxUint64/10 && delta > kMaxUint64%10)) {
                                                     ^
[ 62%] Building CXX object vendor/leveldb-1.12.0/CMakeFiles/leveldb.dir/util/options.cc.o
[ 62%] Building CXX object vendor/leveldb-1.12.0/CMakeFiles/leveldb.dir/util/status.cc.o
[ 63%] Building CXX object vendor/leveldb-1.12.0/CMakeFiles/leveldb.dir/table/block.cc.o
[ 63%] Building CXX object vendor/leveldb-1.12.0/CMakeFiles/leveldb.dir/table/block_builder.cc.o
[ 64%] Building CXX object vendor/leveldb-1.12.0/CMakeFiles/leveldb.dir/table/filter_block.cc.o
/root/bitshares_toolkit/vendor/leveldb-1.12.0/table/filter_block.cc: In member function ‘bool leveldb::FilterBlockReader::KeyMayMatch(uint64_t, const leveldb::Slice&)’:
/root/bitshares_toolkit/vendor/leveldb-1.12.0/table/filter_block.cc:100:52: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
     if (start <= limit && limit <= (offset_ - data_)) {
                                                    ^
[ 64%] Building CXX object vendor/leveldb-1.12.0/CMakeFiles/leveldb.dir/table/format.cc.o
[ 65%] Building CXX object vendor/leveldb-1.12.0/CMakeFiles/leveldb.dir/table/iterator.cc.o
[ 65%] Building CXX object vendor/leveldb-1.12.0/CMakeFiles/leveldb.dir/table/merger.cc.o
[ 66%] Building CXX object vendor/leveldb-1.12.0/CMakeFiles/leveldb.dir/table/table.cc.o
[ 66%] Building CXX object vendor/leveldb-1.12.0/CMakeFiles/leveldb.dir/table/table_builder.cc.o
[ 67%] Building CXX object vendor/leveldb-1.12.0/CMakeFiles/leveldb.dir/table/two_level_iterator.cc.o
Linking CXX static library libleveldb.a
[ 67%] Built target leveldb
Scanning dependencies of target bts_db
[ 68%] Building CXX object libraries/db/CMakeFiles/bts_db.dir/upgrade_leveldb.cpp.o
In file included from /root/bitshares_toolkit/libraries/db/include/bts/db/exception.hpp:2:0,
                 from /root/bitshares_toolkit/libraries/db/upgrade_leveldb.cpp:1:
/root/bitshares_toolkit/libraries/fc/include/fc/exception/exception.hpp: In instantiation of ‘void fc::exception_factory::register_exception() [with T = bts::db::db_exception]’:
/root/bitshares_toolkit/libraries/db/upgrade_leveldb.cpp:9:5:   required from here
/root/bitshares_toolkit/libraries/fc/include/fc/exception/exception.hpp:184:17: warning: variable ‘itr’ set but not used [-Wunused-but-set-variable]
            auto itr = _registered_exceptions.find( T::code_value );
                 ^
/root/bitshares_toolkit/libraries/fc/include/fc/exception/exception.hpp: In instantiation of ‘void fc::exception_factory::register_exception() [with T = bts::db::db_in_use_exception]’:
/root/bitshares_toolkit/libraries/db/upgrade_leveldb.cpp:9:5:   required from here
/root/bitshares_toolkit/libraries/fc/include/fc/exception/exception.hpp:184:17: warning: variable ‘itr’ set but not used [-Wunused-but-set-variable]
Linking CXX static library libbts_db.a
[ 68%] Built target bts_db
Scanning dependencies of target bts_utilities
[ 69%] Building CXX object libraries/utilities/CMakeFiles/bts_utilities.dir/key_conversion.cpp.o
[ 69%] Building CXX object libraries/utilities/CMakeFiles/bts_utilities.dir/string_escape.cpp.o
[ 70%] Building CXX object libraries/utilities/CMakeFiles/bts_utilities.dir/git_revision.cpp.o
Linking CXX static library libbts_utilities.a
[ 70%] Built target bts_utilities
Scanning dependencies of target bts_api_generator
[ 71%] Building CXX object libraries/api/CMakeFiles/bts_api_generator.dir/bts_api_generator.cpp.o
Linking CXX executable bts_api_generator
[ 71%] Built target bts_api_generator
[ 72%] Generating include/bts/api/common_api.hpp, ../rpc_stubs/common_api_rpc_server.cpp, ../rpc_stubs/common_api_rpc_client.cpp, ../rpc_stubs/common_api_client.cpp, ../rpc_stubs/include/bts/rpc_stubs/common_api_rpc_server.hpp, ../rpc_stubs/include/bts/rpc_stubs/common_api_rpc_client.hpp, ../rpc_stubs/include/bts/rpc_stubs/common_api_client.hpp, ../rpc_stubs/include/bts/rpc_stubs/common_api_overrides.ipp
Scanning dependencies of target bts_api
[ 72%] Building CXX object libraries/api/CMakeFiles/bts_api.dir/conversion_functions.cpp.o
Linking CXX static library libbts_api.a
[ 72%] Built target bts_api
Scanning dependencies of target bts_blockchain
[ 72%] Building CXX object libraries/blockchain/CMakeFiles/bts_blockchain.dir/time.cpp.o
[ 73%] Building CXX object libraries/blockchain/CMakeFiles/bts_blockchain.dir/extended_address.cpp.o
[ 73%] Building CXX object libraries/blockchain/CMakeFiles/bts_blockchain.dir/address.cpp.o
[ 74%] Building CXX object libraries/blockchain/CMakeFiles/bts_blockchain.dir/pts_address.cpp.o
[ 74%] Building CXX object libraries/blockchain/CMakeFiles/bts_blockchain.dir/asset.cpp.o
[ 75%] Building CXX object libraries/blockchain/CMakeFiles/bts_blockchain.dir/types.cpp.o
[ 75%] Building CXX object libraries/blockchain/CMakeFiles/bts_blockchain.dir/operations.cpp.o
[ 76%] Building CXX object libraries/blockchain/CMakeFiles/bts_blockchain.dir/withdraw_types.cpp.o
[ 76%] Building CXX object libraries/blockchain/CMakeFiles/bts_blockchain.dir/pending_chain_state.cpp.o
[ 77%] Building CXX object libraries/blockchain/CMakeFiles/bts_blockchain.dir/transaction.cpp.o
[ 77%] Building CXX object libraries/blockchain/CMakeFiles/bts_blockchain.dir/chain_interface.cpp.o
[ 78%] Building CXX object libraries/blockchain/CMakeFiles/bts_blockchain.dir/block.cpp.o
[ 78%] Building CXX object libraries/blockchain/CMakeFiles/bts_blockchain.dir/chain_database.cpp.o
In file included from /root/bitshares_toolkit/libraries/blockchain/include/bts/blockchain/exceptions.hpp:2:0,
                 from /root/bitshares_toolkit/libraries/blockchain/chain_database.cpp:1:
/root/bitshares_toolkit/libraries/fc/include/fc/exception/exception.hpp: In instantiation of ‘void fc::exception_factory::register_exception() [with T = bts::blockchain::invalid_pts_address]’:
/root/bitshares_toolkit/libraries/blockchain/chain_database.cpp:94:4:   required from here
/root/bitshares_toolkit/libraries/fc/include/fc/exception/exception.hpp:184:17: warning: variable ‘itr’ set but not used [-Wunused-but-set-variable]
            auto itr = _registered_exceptions.find( T::code_value );
                 ^
/root/bitshares_toolkit/libraries/fc/include/fc/exception/exception.hpp: In instantiation of ‘void fc::exception_factory::register_exception() [with T = bts::blockchain::addition_overflow]’:
/root/bitshares_toolkit/libraries/blockchain/chain_database.cpp:94:4:   required from here
/root/bitshares_toolkit/libraries/fc/include/fc/exception/exception.hpp:184:17: warning: variable ‘itr’ set but not used [-Wunused-but-set-variable]
/root/bitshares_toolkit/libraries/fc/include/fc/exception/exception.hpp: In instantiation of ‘void fc::exception_factory::register_exception() [with T = bts::blockchain::addition_underthrow]’:
/root/bitshares_toolkit/libraries/blockchain/chain_database.cpp:94:4:   required from here
/root/bitshares_toolkit/libraries/fc/include/fc/exception/exception.hpp:184:17: warning: variable ‘itr’ set but not used [-Wunused-but-set-variable]
/root/bitshares_toolkit/libraries/fc/include/fc/exception/exception.hpp: In instantiation of ‘void fc::exception_factory::register_exception() [with T = bts::blockchain::asset_type_mismatch]’:
/root/bitshares_toolkit/libraries/blockchain/chain_database.cpp:94:4:   required from here
/root/bitshares_toolkit/libraries/fc/include/fc/exception/exception.hpp:184:17: warning: variable ‘itr’ set but not used [-Wunused-but-set-variable]
[ 79%] Building CXX object libraries/blockchain/CMakeFiles/bts_blockchain.dir/fire_operation.cpp.o
[ 79%] Building CXX object libraries/blockchain/CMakeFiles/bts_blockchain.dir/account_record.cpp.o
Linking CXX static library libbts_blockchain.a
[ 79%] Built target bts_blockchain
Scanning dependencies of target bitcoin
[ 79%] Building CXX object libraries/bitcoin/CMakeFiles/bitcoin.dir/armory.cpp.o
[ 80%] Building CXX object libraries/bitcoin/CMakeFiles/bitcoin.dir/bitcoin.cpp.o
[ 80%] Building CXX object libraries/bitcoin/CMakeFiles/bitcoin.dir/electrum.cpp.o
c++: internal compiler error: Killed (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-4.8/README.Bugs> for instructions.
make[2]: *** [libraries/bitcoin/CMakeFiles/bitcoin.dir/electrum.cpp.o] Error 4
make[1]: *** [libraries/bitcoin/CMakeFiles/bitcoin.dir/all] Error 2
make: *** [all] Error 2
root@xt:~/bitshares_toolkit#

Probably out of memory, try a bigger node
Title: Re: Initial delegates, let's get ready!
Post by: bitcoinerS on June 08, 2014, 04:51:11 am
Node: VPS server Ubuntu 14.04, 2 GB RAM (RAM can be increased as needed)
Location: NYC


bitcoiners-1: XTS8UmCBubeC28XGUG1THcwaeqAmGNnP47R4GNzmVXLNCbk46SMkd
bitcoiners-2: XTS6ezsAe72hVoMq4mC4fnAAF2XYqprcpt4vZ5nkqUoZn8xsSWB5Z
bitcoiners-3: XTS72Xc5wBYmWQrAqcPoU6RSEegB3CosNh82wbf4QkKquJtbhgPWL
bitcoiners-4: XTS7DeMWhGV8P7oiKoigtGqFKDfauB83Nrxy5FpMwLEjMw7wC8UVe
bitcoiners-5: XTS73iK3RkkijdfgzH5mioB4wzWFNsmsvwtsNPnkoHAApHK6cbMz3
Title: Re: Initial delegates, let's get ready!
Post by: bitcoinerS on June 08, 2014, 04:54:38 am
Keep getting compile error on Ubuntu server 14.04

make clean; make
does not help

Code: [Select]
71%] Built target bts_api_generator
[ 72%] Generating include/bts/api/common_api.hpp, ../rpc_stubs/common_api_rpc_server.cpp, ../rpc_stubs/common_api_rpc_client.cpp, ../rpc_stubs/common_api_client.cpp, ../rpc_stubs/include/bts/rpc_stubs/common_api_rpc_server.hpp, ../rpc_stubs/include/bts/rpc_stubs/common_api_rpc_client.hpp, ../rpc_stubs/include/bts/rpc_stubs/common_api_client.hpp, ../rpc_stubs/include/bts/rpc_stubs/common_api_overrides.ipp
terminate called after throwing an instance of 'std::runtime_error'
  what():  locale::facet::_S_create_c_locale name not valid
Aborted
make[2]: *** [libraries/api/include/bts/api/common_api.hpp] Error 134
make[1]: *** [libraries/api/CMakeFiles/bts_api.dir/all] Error 2
make: *** [all] Error 2
Title: Re: Initial delegates, let's get ready!
Post by: toast on June 08, 2014, 05:00:57 am
Keep getting compile error on Ubuntu server 14.04

make clean; make
does not help

Code: [Select]
71%] Built target bts_api_generator
[ 72%] Generating include/bts/api/common_api.hpp, ../rpc_stubs/common_api_rpc_server.cpp, ../rpc_stubs/common_api_rpc_client.cpp, ../rpc_stubs/common_api_client.cpp, ../rpc_stubs/include/bts/rpc_stubs/common_api_rpc_server.hpp, ../rpc_stubs/include/bts/rpc_stubs/common_api_rpc_client.hpp, ../rpc_stubs/include/bts/rpc_stubs/common_api_client.hpp, ../rpc_stubs/include/bts/rpc_stubs/common_api_overrides.ipp
terminate called after throwing an instance of 'std::runtime_error'
  what():  locale::facet::_S_create_c_locale name not valid
Aborted
make[2]: *** [libraries/api/include/bts/api/common_api.hpp] Error 134
make[1]: *** [libraries/api/CMakeFiles/bts_api.dir/all] Error 2
make: *** [all] Error 2

looks like you got farther but now you are on an error I have never seen before, and google doesn't help. will check it out after I sleep
Title: Re: Initial delegates, let's get ready!
Post by: sfinder on June 08, 2014, 05:10:36 am
pan2pan-01:  XTS6tmvXdn2vJss4a4ADVUUi8GbAC37H6HJRcVeFyhzcsRUNyQJGE
pan2pan-02:  XTS5vXkQbGLEwaye3ZsLAtMMEe6tkh724nr2zoGHHeAUCsvVeywvc
pan2pan-03:  XTS5H3qwDsnjm8yoiN1CAQg6LKTnSNuXZDePeGAQSa5CiALSFRFQ8
pan2pan-04:  XTS4u3cQJNLS9jDN1mCM9ynLNHQV9PuEVfwA2R95XnV7ZDNjJL89z
pan2pan-05:  XTS7qHJeGEfMjogPuAnDZ6Vte9nAG7y4hHsM6iXF3aDmN52qz7foT


Name:
Location: Winnipeg, Canada

Hardware:
AMD fx6300
8 GB ddr3 1600mhz ram
500GB HD


Software:

OS Ubuntu server 14.04
Title: Re: Initial delegates, let's get ready!
Post by: Xeldal on June 08, 2014, 05:14:26 am
Node: VPS server Ubuntu 14.04x32, 1GB / 1 CPU 30GB SSD Disk 2TB Transfer
Location: Singapore

XTS5iNWht2kEmdWNDf6cRz6HiVEs2zk3X61GpQvrQT1wQf66xucit
XTS6whTVdWVb4KFvBDfKeawRjWPa6rsG5etsMvmg1MuybWhpVTf2u
XTS8QLeHvaYQqFRdTP46EZq4GVdvj65Fp9wbKBGhBx5kvDnNFTDtM
XTS5ttrjXKJPiWYm6EL7LAYRWV4GWnAaBPjGvkydy86yaKQdxTcHg
XTS51zjQsZyb4oYnPe6272bENc4aefshiHVeza3uThwrsL2U3GRMR
Title: Re: Initial delegates, let's get ready!
Post by: alt on June 08, 2014, 05:20:42 am
try
Code: [Select]
VERBOSE=1 make
and post the output

Keep getting compile error on Ubuntu server 14.04

make clean; make
does not help

Code: [Select]
71%] Built target bts_api_generator
[ 72%] Generating include/bts/api/common_api.hpp, ../rpc_stubs/common_api_rpc_server.cpp, ../rpc_stubs/common_api_rpc_client.cpp, ../rpc_stubs/common_api_client.cpp, ../rpc_stubs/include/bts/rpc_stubs/common_api_rpc_server.hpp, ../rpc_stubs/include/bts/rpc_stubs/common_api_rpc_client.hpp, ../rpc_stubs/include/bts/rpc_stubs/common_api_client.hpp, ../rpc_stubs/include/bts/rpc_stubs/common_api_overrides.ipp
terminate called after throwing an instance of 'std::runtime_error'
  what():  locale::facet::_S_create_c_locale name not valid
Aborted
make[2]: *** [libraries/api/include/bts/api/common_api.hpp] Error 134
make[1]: *** [libraries/api/CMakeFiles/bts_api.dir/all] Error 2
make: *** [all] Error 2
Title: Re: Initial delegates, let's get ready!
Post by: bitcoinerS on June 08, 2014, 05:46:11 am
here it is

try

VERBOSE=1 make



Code: [Select]

Linking CXX executable bts_api_generator
cd /root/bitshares_toolkit/libraries/api && /usr/bin/cmake -E cmake_link_script CMakeFiles/bts_api_generator.dir/link.txt --verbose=1
/usr/bin/c++    -std=c++11 -Wall  -O2 -g -DNDEBUG    CMakeFiles/bts_api_generator.dir/bts_api_generator.cpp.o  -o bts_api_generator -rdynamic ../fc/libfc.a ../utilities/libbts_utilities.a ../../vendor/leveldb-1.12.0/libleveldb.a -lrt ../fc/libfc.a ../fc/vendor/easylzma/src/libeasylzma_static.a -Wl,-Bstatic -lboost_thread -lboost_date_time -lboost_system -lboost_filesystem -lboost_program_options -lboost_signals -lboost_serialization -lboost_chrono -lboost_unit_test_framework -lboost_context -lboost_locale -lboost_coroutine -Wl,-Bdynamic -lpthread -Wl,-Bstatic -lssl -lcrypto -Wl,-Bdynamic -lz -ldl -lpthread
make[2]: Leaving directory `/root/bitshares_toolkit'
/usr/bin/cmake -E cmake_progress_report /root/bitshares_toolkit/CMakeFiles  4
[ 71%] Built target bts_api_generator
make -f libraries/api/CMakeFiles/bts_api.dir/build.make libraries/api/CMakeFiles/bts_api.dir/depend
make[2]: Entering directory `/root/bitshares_toolkit'
/usr/bin/cmake -E cmake_progress_report /root/bitshares_toolkit/CMakeFiles 3
[ 72%] Generating include/bts/api/common_api.hpp, ../rpc_stubs/common_api_rpc_server.cpp, ../rpc_stubs/common_api_rpc_client.cpp, ../rpc_stubs/common_api_client.cpp, ../rpc_stubs/include/bts/rpc_stubs/common_api_rpc_server.hpp, ../rpc_stubs/include/bts/rpc_stubs/common_api_rpc_client.hpp, ../rpc_stubs/include/bts/rpc_stubs/common_api_client.hpp, ../rpc_stubs/include/bts/rpc_stubs/common_api_overrides.ipp
cd /root/bitshares_toolkit/libraries/api && ./bts_api_generator --api-classname=common_api --api-interface-output-dir=/root/bitshares_toolkit/libraries/api --rpc-stub-output-dir=/root/bitshares_toolkit/libraries/rpc_stubs /root/bitshares_toolkit/libraries/api/types.json /root/bitshares_toolkit/libraries/api/blockchain_api.json /root/bitshares_toolkit/libraries/api/wallet_api.json /root/bitshares_toolkit/libraries/api/network_api.json /root/bitshares_toolkit/libraries/api/bitcoin_api.json /root/bitshares_toolkit/libraries/api/general_api.json
terminate called after throwing an instance of 'std::runtime_error'
  what():  locale::facet::_S_create_c_locale name not valid
Aborted
make[2]: *** [libraries/api/include/bts/api/common_api.hpp] Error 134
make[2]: Leaving directory `/root/bitshares_toolkit'
make[1]: *** [libraries/api/CMakeFiles/bts_api.dir/all] Error 2
make[1]: Leaving directory `/root/bitshares_toolkit'
make: *** [all] Error 2




Title: Re: Initial delegates, let's get ready!
Post by: puppies on June 08, 2014, 05:52:19 am
Another test net is up right now - just a test test network, we will do the real dry-run when we have more delegates

puppies, emski, your 10 keys are registered as initial delegates.
sfinder, for some reason Dan didn't see your post. Whoops. You'll get into the real dry run with everyone else.

puppies and emski should:

1) Pull latest (+ git submodule update) and build
2) Wipe data dir
3) "wallet_create" / "wallet_unlock 9999999"
4) "wallet_import_private_key <WIF_PRIVATE_KEY>" on each key (other readers: you must "wallet_account_create" first if you are not hard-coded delegate)
5) "rescan"

Leave it running for a while (50 minutes worst case)

6) "blockchain_get_delegates"  -> see the names of all your delegats
7) "blockchain_get_account_record <delegate_name>"

"blocks_produced" should be more than 0.
"blocks_missed" will be big but should stop increasing after you import your keys

Thanks Toast.

Up, running, and producing blocks.
Title: Re: Initial delegates, let's get ready!
Post by: puppies on June 08, 2014, 06:27:32 am
For those of you having build issues.   I had similar looking errors (i didn't copy them) when attempting to build on a vm with less than 2gb of ram.   Try increasing ram to 2gb and build again.   If that doesn't work you will have to wait for the experts.
Title: Re: Initial delegates, let's get ready!
Post by: denkhaus on June 08, 2014, 06:28:21 am
Node specs:
Server in Germany. 4G RAM (increasable), 256 GB SSD, Ubuntu 12.04 LTS

Keys:
denkhaus-delegate-1: XTS6snqX6msDPGuk6V8W5AXDtpaLLFUAjUFjM7LSSqyx7D9zJ65PY
denkhaus-delegate-2: XTS6v9Dt9Yz4XyMaiQLzKqS7V2LwVMj2KYHL7Bqeg7f7QEaRb7CHR
denkhaus-delegate-3: XTS5fXuqAN8cSpkmGaf4vSGA2fgojch2ZF5PcSxqnx2yw7sZ8rWGW
denkhaus-delegate-4: XTS7LV8XA8cXPb5y7DBGqdDMV8sV2cXsdimCq3oxPvwm3heHa67jY
denkhaus-delegate-5: XTS8kAZ2CG1WF1gSPpRLNH1Sx9ggYX1s3QEQ5fBYU6gQjpvhMwMCj
Title: Re: Initial delegates, let's get ready!
Post by: emski on June 08, 2014, 06:49:48 am
Got the following error:

established outbound connection to 107.170.30.182:8764                      node.cpp:488
Sent "hello" to peer 107.170.30.182:8764                    node.cpp:2042
The hello message I just sent contains connection information: my_ip: XXXXXXXXXXX, my_outbound_port: 5678, my_inbound_port: 5678

Received a rejection from 107.170.30.182:8764 in response to my "hello", reason: "You're on a different chain than I am.  I'm on 3b7df0e87c4f3b1ff36f48f4f374ea6c52355626c31962e50c73552390704e67 and you're on 5b4b4e70614f80b5b88392ff33ebf194e53e4ed9bf2fd43c233c1f7e470a2981"

What can I do about this?

I've updated and rebuilt according to instructions.

I've also tried titan branch:

1618537ms       th_a on_connection_reject ] Received a rejection in response to my "hello"                      node.cpp:1257
1618537ms       th_a            read_loop ] disconnected eof
End of file
    {"message":"End of file"}
    asio  asio.cpp:22 read_write_handler

    {"len":16}
    th_a  stcp_socket.cpp:73 readsome                   message_oriented_connection.cpp:130
1618537ms       th_a on_connection_closed ] Remote peer 107.170.30.182:8764 closed their connection to us                       node.cpp:1608

Title: Re: Initial delegates, let's get ready!
Post by: taoljj on June 08, 2014, 06:50:30 am
location: China
os: ubuntu14.04
cpu: Intel I3
mem: 4G

taoljj-delegate-1: XTS7xQtXcZuNn5RgyPdvtfsYAJXS8bysihvrCsvuNC6twdRNxPFA7
taoljj-delegate-2: XTS8NY1vLakvjzdJHmcia3CByapQJZCnNdk6hLMd1numLck6Tc9oc
taoljj-delegate-3: XTS6mqjSDW67NQSAwZ8Tq5Kctg2Xr8sky5VtZePUQASCZ8xf5ha7L
taoljj-delegate-4: XTS8U4v6VdxQehFqfVv5r4FN4mQKd1vTsAidbBRiMx617GdR4epVT
taoljj-delegate-5: XTS6Go5mzcJw4wBWkYmqz6ra2G1nJDVebcAuqocHmjKB7BfXTPF6S
Title: Re: Initial delegates, let's get ready!
Post by: puppies on June 08, 2014, 07:43:21 am
Got the following error:

established outbound connection to 107.170.30.182:8764                      node.cpp:488
Sent "hello" to peer 107.170.30.182:8764                    node.cpp:2042
The hello message I just sent contains connection information: my_ip: XXXXXXXXXXX, my_outbound_port: 5678, my_inbound_port: 5678

Received a rejection from 107.170.30.182:8764 in response to my "hello", reason: "You're on a different chain than I am.  I'm on 3b7df0e87c4f3b1ff36f48f4f374ea6c52355626c31962e50c73552390704e67 and you're on 5b4b4e70614f80b5b88392ff33ebf194e53e4ed9bf2fd43c233c1f7e470a2981"

What can I do about this?

I've updated and rebuilt according to instructions.

I've also tried titan branch:

1618537ms       th_a on_connection_reject ] Received a rejection in response to my "hello"                      node.cpp:1257
1618537ms       th_a            read_loop ] disconnected eof
End of file
    {"message":"End of file"}
    asio  asio.cpp:22 read_write_handler

    {"len":16}
    th_a  stcp_socket.cpp:73 readsome                   message_oriented_connection.cpp:130
1618537ms       th_a on_connection_closed ] Remote peer 107.170.30.182:8764 closed their connection to us                       node.cpp:1608

I am totally confused.  We are going to have to wait for the people that actually understand all this stuff to wake up.  My bitshares_client doesn't throw any errors, and network_get_connection_count shows 1.  Network_get_peer_info shows
Quote
[{
    "addr": "107.170.30.182:8764",
    "addrlocal": "107.170.170.214:34021",
    "services": "00000001",
    "lastsend": 1402212502,
    "lastrecv": 1402212502,
    "bytessent": 9520,
    "bytesrecv": 46800,
    "conntime": "",
    "pingtime": "",
    "pingwait": "",
    "version": "",
    "subver": "bts::net::node",
    "inbound": false,
    "firewall_status": "unknown",
    "startingheight": "",
    "banscore": "",
    "syncnode": "",
    "bitshares_git_revision_sha": "34f677e17217a1a1f0eb17f6aaa9296bf259b217 (different from ours)",
    "bitshares_git_revision_unix_timestamp": "20140608T020517",
    "bitshares_git_revision_age": "5 hours ago (older than ours)",
    "fc_git_revision_sha": "ac6505f196c9a360957af2f9fa4814a814261bbf (different from ours)",
    "fc_git_revision_unix_timestamp": "20140608T010812",
    "fc_git_revision_age": "6 hours ago (older than ours)",
    "platform": "linux"
  }

and blockchain_get_config shows
Quote
{
  "blockchain_id": "3b7df0e87c4f3b1ff36f48f4f374ea6c52355626c31962e50c73552390704e67",
  "block_interval": 15,
  "max_block_size": 104857,
  "target_block_size": 52428,
  "max_blockchain_size": 107374182400,
  "symbol": "XTS",
  "version": 101,
  "min_block_fee": 1,
  "delegate_num": 97,
  "delegate_reg_fee": 1000000,
  "delegate_reward_min": 10000,
  "name_size_max": 63,
  "data_size_max": 4096,
  "asset_reg_fee": 1000000,
  "asset_shares_max": 1000000000000000
}

I'm not sure I'm connected to the main chain at all anymore.  My delegates are still producing blocks, but I don't know of a real time way of seeing if blocks are being generated by other delegates.  I do show blocks generated by the always present delegate91.

Either way I am going to sleep.
Title: Re: Initial delegates, let's get ready!
Post by: coolspeed on June 08, 2014, 08:22:03 am
Location: San Francisco, USA.
CPU: 4 core precessor
RAM: 8GB
SSD hard disk.

Public keys:

coolspeed-delegate-1 : XTS6DitjvvENF6Frfvb1jiUCNAGNwH6PMjYVEGCxAvV4cZXRVbwmp
coolspeed-delegate-2 : XTS7AeUKLhpn2J5rekbFdCt3xsJ5SznRL5bR5kEBT7JSbCB9AQFka
coolspeed-delegate-3 : XTS6uVAGPTgbrdVnx9b5qMRqoVakVBMZymVWWDJy6QmuMrDnySHmg
coolspeed-delegate-4 : XTS5kJVSkqGbPXUCfyz2kfXj6ZSBeV7xbXdhmBsJ8FQ8kjY4iANmM
coolspeed-delegate-5 : XTS7XDCb4BEeEtbPtHWGCvx9xW3r5SGTrHr8PjnH3VbhtUFWsjArm

Title: Re: Initial delegates, let's get ready!
Post by: xeroc on June 08, 2014, 08:56:22 am
xeroc-delegate-1: XTS6DTmCuhUgGyN3sE2qxe7x21Fon9yqYrn9nErGLVqpiRJg9MvAH
xeroc-delegate-2: XTS8Y443qpsYp5hpmczg7NvDtqumZvzP8Az88n2EDrKECzYJKwMDP
xeroc-delegate-3: XTS5dLdpSdVZEcT7JNFL6Q7CJ8kxxj2geX7xCNJRhAK543gULNoK2
xeroc-delegate-4: XTS5oSzGcPetswPJSQ9s9qoXRdfax1oVVWCZsaKnBS5Q8u7gawZ6B
xeroc-delegate-5: XTS7e4pNDgLy7C7T6haye45PLrTRvH9FfAKpj8BAS3fbXNd6EtYEM


//edit: git-master running with accounts set up

Location: Germany
fat client :-)
Title: Re: Initial delegates, let's get ready!
Post by: Troglodactyl on June 08, 2014, 09:14:23 am
Location: Texas, USA
CPU: 3.4Ghz quad core
RAM: 8GB

troglodactyl-delegate-1: XTS5DmPZBzrAxmQ5CQHQxfZ5fLWKVJ1kDvdqcBYbwBm7nuqBEcFX2
troglodactyl-delegate-2: XTS8aNGydnsjGn2YH7xEvocgYF2tC6zTnuLosqYJ9DyD9n3sfrxGC
troglodactyl-delegate-3: XTS5EVghckGywFQL4StpqMiYEiRJvpSKBUUe35ePL4RMyDcwk97ko
troglodactyl-delegate-4: XTS8TouigRWFaQ8Bxt5YrPQJwR77RKFuCmbs5hTtuiQbzgNexwzef
troglodactyl-delegate-5: XTS66egtaE9cVPqzNYew5tu2zYjGMroFUTHJYZfRmUukezVxEQ7mF
Title: Re: Initial delegates, let's get ready!
Post by: testz on June 08, 2014, 09:17:56 am
testz-delegate-1: XTS7TmBWefbLK7YHXUkt94SuxPksPSEpzqxcLY2ATgUYc3tK2en4h
testz-delegate-2: XTS69fowDK5omSewZWFwms2BcjbsxRrjxHeZ78GQzWA8jpBDAjffx
testz-delegate-3: XTS6wcaRaGviNzVdCdUYCdJywq283QRgbxcnSGGKZ9dhck96aQTzE
testz-delegate-4: XTS8J1Anw53eW99eT3nipNVrx2E82P9p24Pbqz1KvgFPqenNXPPvS
testz-delegate-5: XTS65uHPoa3x8x45Cf3ZHdS7Jkr2uSCfHotFsu3SgWaZDgjqBGNQr

DNS Name: cryptoseed.cloudapp.net:8764
Location: Cloud
Hardware: Azure VM
Title: Re: Initial delegates, let's get ready!
Post by: svk on June 08, 2014, 09:52:46 am
svk-delegate-1: XTSPC2qa4snEatrz7coSLMsyHdH8n2uaQLsz
svk-delegate-2: XTS8WCd3V4QRsWW79J9SbGHWkZZrZpVskSpc
svk-delegate-3: XTS9bAPKsBQT2NHoADqxQHFAr7v1QQNDne5J
svk-delegate-4: XTSBbGnohrKfS214De29gcc9m28cUMcBTLP
svk-delegate-5: XTS9Ez7UASJsY7LZfDmZxyoJFGzStjxv9s65

Location: France
Ubuntu 14.04 VM
i3 2.1 2gb RAM
SSD
1GB Fiber Internet


















Title: Re: Initial delegates, let's get ready!
Post by: JoeyD on June 08, 2014, 09:56:00 am
VPS
2 cores Xeon
4Gb Ram
150 Gb ssd
All upgradeable.

Location: Netherlands

I will generate the keys and add them here when I get home later today, I'm not comfortable with generating keys via a webinterface on the vps itself and need to setup a good encrypted storage system.

In the meantime what ports need to be opened in the firewall? I'm quickly losing the few connections I have, either with warnings in the log about them delivering rejected blocks or because of them being suspected of being firewalled. Currently I'm on block 179 with 0 network_num_connections.

Any advice for good encryption software as an alternative for the apparently compromised truecrypt that works with usbstorage, or is everyone using pgp/ecryptfs?

Also for DDoS protection, do you have any estimates on the traffic numbers per ip for a delegate, so I can setup a rate limited ufw-configuration?

EDIT
I'm still getting new blocks, are connections supposed to be permanent or are they intermittent? In the log I'm also seeing local-lan ip-addresses, so I'm guessing some configuration tweaks need to be made, plus instructions on what ports to forward.
Title: Re: Initial delegates, let's get ready!
Post by: changematey on June 08, 2014, 10:40:06 am
I am not really a technically inclined guy so have followed the instructions here:
https://github.com/nmushegian/bitshares_toolkit/blob/master/BUILD_UBUNTU.md

when I do cmake, it just tells me parameters. After which when I run make:
Quote
ubuntu@:~/bitshares_toolkit$ make
make: *** No targets specified and no makefile found.  Stop.
Title: Re: Initial delegates, let's get ready!
Post by: emski on June 08, 2014, 10:59:36 am
I am not really a technically inclined guy so have followed the instructions here:
https://github.com/nmushegian/bitshares_toolkit/blob/master/BUILD_UBUNTU.md

when I do cmake, it just tells me parameters. After which when I run make:
Quote
ubuntu@:~/bitshares_toolkit$ make
make: *** No targets specified and no makefile found.  Stop.

cmake . | note the dot
make
Title: Re: Initial delegates, let's get ready!
Post by: changematey on June 08, 2014, 11:30:44 am
I am not really a technically inclined guy so have followed the instructions here:
https://github.com/nmushegian/bitshares_toolkit/blob/master/BUILD_UBUNTU.md

when I do cmake, it just tells me parameters. After which when I run make:
Quote
ubuntu@:~/bitshares_toolkit$ make
make: *** No targets specified and no makefile found.  Stop.

cmake . | note the dot
make
Thanks :)

Location: Sydney, Australia
Amazon EC2

changematey1: XTS5o34s2DQsWc42GHUW9baTkSj7kB6Ma6QrbD9GtMPNvhBuddPDE
changematey2: XTS7gfVaWV5v1A7Nzh5fCfjLRWRvjGX4w5tqM5pcxSnbvvaARM4wT
changematey3: XTS8QS83EwD9N9LVDQycNLc9d9e8GkkY7Cy8LtsDVDF9meskrwL2m
changematey4: XTS8YUSi45yoRoRL6UQEqyhE4GoNxW2kKLdzxWnDPs9MhSkT5yTgU
changematey5: XTS7L3qc1JHx4gX7EmPK1AKJXtnEJfbry2saHQJjfFZd76RH5pTpY
Title: Re: Initial delegates, let's get ready!
Post by: emski on June 08, 2014, 11:58:55 am
After checking the reply of puppies I noticed that the seed node is running revision 34f677e17217a1a1f0eb17f6aaa9296bf259b217 of github repo (github.com/BitShares/bitshares_toolki).
Which is different than the latest in master.
I did a checkout of that specific revision and everything seems to be working fine now.

I would really like to see the exact revision you are going to use next time. It will save me some time troubleshooting.

Title: Re: Initial delegates, let's get ready!
Post by: zhangweis on June 08, 2014, 12:18:04 pm
Node: 1 Core CPU/2G memory/20G SSD
Location: Qingdao, China

Public keys:
zhangweis-delegate-1:XTS6sSu1DhZUxpnoLz1wYvwsowUQpa4zyHFkqo972fKnU6xrEKVx8
zhangweis-delegate-2:XTS7CoMc1xHodpiVYS8gukQRhmrpxaBEz7oMaUy434HBLbJegtFo1
zhangweis-delegate-3:XTS7kcfTvho6h7juwajcNxBQA9rmiqd5iSFMZYywwbWRk9wqjo2Np
zhangweis-delegate-4:XTS6yyGEujvofqgQRfwvwWxMjZiFJwE4kBE1BpXtGpmhZ8aC58Dmb
zhangweis-delegate-5:XTS4yrt2mFvEcaNCD3HVYiDgWcS5jVpf3R9MfnTh6W3v3Y1W4vGrA

(repost)
Title: Re: Initial delegates, let's get ready!
Post by: alexxy on June 08, 2014, 12:18:42 pm
My location is Russia, St.Petersburg
HW: gentoo node running on core i5

alexxy-delegate-1 XTS6DhvyoGMM6GiEfQ7UbrXXKiQCnofCk9ZTdzTRdswtM3Ttx6Dvm
alexxy-delegate-2 XTS5vTKdk2HX4GCBJ7HNHJk1fnRZao4mYRiJAU2462oGX9e2fcmaz
alexxy-delegate-3 XTS7wNbAFwpMerMszHjY7L3hGFmZtmS9MFGapcPQx7S5w7mBMBdrm
alexxy-delegate-4 XTS6ATqGY8ynvL7cqHsxCJYuNYRLX7Nyv9X51qT6MivTADt6dPMRc
alexxy-delegate-5 XTS6CZpnNrYT4uAxJPFAXRS5U8gKZTF4Z4sSEBjMTMwoYZbmirNc3

IF needed i can run seed node for ipv4 and ipv6 networks
Title: Re: Initial delegates, let's get ready!
Post by: liondani on June 08, 2014, 12:53:25 pm
have you delete my first reply? ...why?

I 'l give the public keys here...
Title: Re: Initial delegates, let's get ready!
Post by: metalallen on June 08, 2014, 01:19:58 pm
Code: [Select]
root@rrz:~/bitshares_toolkit# cmake .
CMake Error at CMakeLists.txt:3 (cmake_minimum_required):
  CMake 2.8.12 or higher is required.  You are running version 2.8.7


-- Configuring incomplete, errors occurred!

how to solve this problem?

and how to generate public key? I'm lost, just want to join the test.
Title: Re: Initial delegates, let's get ready!
Post by: spartako on June 08, 2014, 01:44:14 pm
Code: [Select]
root@rrz:~/bitshares_toolkit# cmake .
CMake Error at CMakeLists.txt:3 (cmake_minimum_required):
  CMake 2.8.12 or higher is required.  You are running version 2.8.7


-- Configuring incomplete, errors occurred!

how to solve this problem?

and how to generate public key? I'm lost, just want to join the test.

You need to install a more recent version of cmake >=  2.8.12
Title: Re: Initial delegates, let's get ready!
Post by: mauritso on June 08, 2014, 02:09:35 pm
I can't get it to build correctly on windows, if someone can get it to work, please upload the binaries somewhere and share it.

Running at this moment:

Hardware: Intel i7 2675QM 2.2Ghz / 16GB RAM
Software: Mac OS X 10.9.3
Network: 180mbps down / 18 mbps up
Location: Netherlands

If I can get a working bitshares client on windows:

Hardware: AMD A10 7850K / 8GB RAM / 64GB SSD
Software: Windows 8.1
Network: 180mbps down / 18 mbps up
Location: Netherlands

Or else I will run it in a Virtualbox VM with 3GB RAM and ubuntu server on this hardware.

If needed and/or at the start of the real XT network I will fire up an Amazon EC2 M3.medium / M3.large instance (location: Anywhere ;)

The names are what I will register the keys as.

mauritso-delegate-1: XTS6VeDfUq4kT37yzWJs5stJEM3F11i1v6xghQBZYrFENp4aE843y
mauritso-delegate-2: XTS8H3yYSA39YNjTtVbeeoy9gPAdTg9ZKgMR7dhbiiao4JeMGnfia
mauritso-delegate-3: XTS6eU9M5uRVBQGYtkokD6YVvKiaayXu7prY4bkLrN7J1Cm7aZerZ
mauritso-delegate-4: XTS8B2KDkaHUULJy5kQLq2Su5ZD8tXrvCYbSWoCgbdPKu7UBWCjMw
mauritso-delegate-5: XTS6aCVDtPLP2eTVnjo9DWctZsg6kcxipfEP57nHsVQXmdPTvwtMq

I can't seem to import the keys using
Code: [Select]
wallet_import_private_key <wif_key> mauritso-delegate-1
wallet_import_private_key <wif_key> mauritso
(mauritso is the wallet that is currently open)

I get:

Code: [Select]
10
is_valid_account( account_name ):
    {}
    th_a  wallet.cpp:785 import_private_key

    {"account_name":"mauritso"}
    th_a  wallet.cpp:812 import_private_key

    {"account_name":"mauritso"}
    th_a  wallet.cpp:831 import_wif_private_key

    {}
    th_a  common_api_client.cpp:212 wallet_import_private_key

    {"command":"wallet_import_private_key"}
    th_a  cli.cpp:574 execute_command

or

Code: [Select]
Unable to decode base58 string wallet_import_private_key
    {"base58_str":"wallet_import_private_key"}
    th_a  base58.cpp:615 from_base58

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

    {}
    th_a  common_api_client.cpp:212 wallet_import_private_key

    {"command":"wallet_import_private_key"}
    th_a  cli.cpp:574 execute_command

when doing wallet_import_private_key and when asked for the privkey giving it the WIF privkey.

Should this be possible and if it is, what am I doing wrong?

I also would like some information about how to run multiple nodes for the same account/delegate effectively. Unlocked/locked wallet, same data/keys or not?
Title: Re: Initial delegates, let's get ready!
Post by: bytemaster on June 08, 2014, 02:21:03 pm
You must create the account before importing the key to the account... this is a point of confusion so I will update the API in this regard.


Code: [Select]
wallet_add_contact_account mauritso-delegate-1 XTS6VeDfUq4kT37yzWJs5stJEM3F11i1v6xghQBZYrFENp4aE843y
wallet_import_private_key ${PRIVATE_KEY FOR XTS6VeDfUq4kT37yzWJs5stJEM3F11i1v6xghQBZYrFENp4aE843y}
Title: Re: Initial delegates, let's get ready!
Post by: alexxy on June 08, 2014, 02:32:19 pm
You must create the account before importing the key to the account... this is a point of confusion so I will update the API in this regard.


Code: [Select]
wallet_add_contact_account mauritso-delegate-1 XTS6VeDfUq4kT37yzWJs5stJEM3F11i1v6xghQBZYrFENp4aE843y
wallet_import_private_key ${PRIVATE_KEY FOR XTS6VeDfUq4kT37yzWJs5stJEM3F11i1v6xghQBZYrFENp4aE843y}

Ok. This works here. But how to import pts wallet? and keyhotee id?
Title: Re: Initial delegates, let's get ready!
Post by: bytemaster on June 08, 2014, 02:41:00 pm
Quote
Unable to decode base58 string wallet_import_private_key

WIF format is the format use by bitcoin for private keys.  They are checksummed and encoded in base 58.

Here is an example of what one looks like.
Code: [Select]
5HwCeJNdh5PCimAZZMwTW4HfbziPbFE4wA5JadXaSRAi4zp3mgA
A HEX format key (what you may be attempting to use) looks like:
Code: [Select]
e2c816b9d29545876580aa5d13d4068d8f0c96554fbd53a2ab7ba63127c9df21
They start with a '5'.   If you need to convert your private key from hex to wif you can use:

Code: [Select]
programs/utils/key_to_wif e2c816b9d29545876580aa5d13d4068d8f0c96554fbd53a2ab7ba63127c9df21
5KYAQufupS3VSVKPLTLHDgXDKUVvhCfWWCvK94B6Er5rKQDckp1
Title: Re: Initial delegates, let's get ready!
Post by: bytemaster on June 08, 2014, 02:42:15 pm
You must create the account before importing the key to the account... this is a point of confusion so I will update the API in this regard.


Code: [Select]
wallet_add_contact_account mauritso-delegate-1 XTS6VeDfUq4kT37yzWJs5stJEM3F11i1v6xghQBZYrFENp4aE843y
wallet_import_private_key ${PRIVATE_KEY FOR XTS6VeDfUq4kT37yzWJs5stJEM3F11i1v6xghQBZYrFENp4aE843y}

Ok. This works here. But how to import pts wallet? and keyhotee id?

Quote
default (unlocked) >>> help wallet_import_bitcoin
Usage:
wallet_import_bitcoin <wallet_filename> <passphrase> <account_name>                                   Imports a bitcoin wallet
Imports a bitcoin wallet

Parameters:
  wallet_filename (filename, required): the bitcoin wallet
  passphrase (passphrase, required): the wallet's password
  account_name (account_name, required): the account name to receive the contents of the wallet
Title: Re: Initial delegates, let's get ready!
Post by: mauritso on June 08, 2014, 02:43:46 pm
Quote
Unable to decode base58 string wallet_import_private_key

WIF format is the format use by bitcoin for private keys.  They are checksummed and encoded in base 58.

Here is an example of what one looks like.
Code: [Select]
5HwCeJNdh5PCimAZZMwTW4HfbziPbFE4wA5JadXaSRAi4zp3mgA
A HEX format key (what you may be attempting to use) looks like:
Code: [Select]
e2c816b9d29545876580aa5d13d4068d8f0c96554fbd53a2ab7ba63127c9df21
They start with a '5'.   If you need to convert your private key from hex to wif you can use:

Code: [Select]
programs/utils/key_to_wif e2c816b9d29545876580aa5d13d4068d8f0c96554fbd53a2ab7ba63127c9df21
5KYAQufupS3VSVKPLTLHDgXDKUVvhCfWWCvK94B6Er5rKQDckp1

Thank you, creating accounts and then adding the keys worked.

That was probably a copy paste error then, I had copied the WIF privkey from the bts_create_key utility.

Is this everything we can do at the moment? Registering accounts/Registering as delegate can't be done until there are funds for that right?
Title: Re: Initial delegates, let's get ready!
Post by: alexxy on June 08, 2014, 03:03:37 pm
Quote
default (unlocked) >>> help wallet_import_bitcoin
Usage:
wallet_import_bitcoin <wallet_filename> <passphrase> <account_name>                                   Imports a bitcoin wallet
Imports a bitcoin wallet

Parameters:
  wallet_filename (filename, required): the bitcoin wallet
  passphrase (passphrase, required): the wallet's password
  account_name (account_name, required): the account name to receive the contents of the wallet

Tryed this, but it crashed after importing 5 of ~30 priv keys
Title: Re: Initial delegates, let's get ready!
Post by: xeroc on June 08, 2014, 03:05:47 pm
BM: how are keyhotee keys imported?
Title: Re: Initial delegates, let's get ready!
Post by: xeroc on June 08, 2014, 03:06:10 pm
can my keyhotee founder code be an initial delegate?
Title: Re: Initial delegates, let's get ready!
Post by: emski on June 08, 2014, 03:19:43 pm
I was toying with the console and the client just shutdown.
Here are the last few lines from the console:
Code: [Select]
emski (unlocked) >>> blockchain_account_record emski
Error: invalid command "blockchain_account_record"
emski (unlocked) >>> blockchain_account_record
shutting down

Here are the last few lines from the log:
Code: [Select]
499387ms       th_a execute_command_line ] blockchain_account_record emski                      cli.cpp:138
499399ms       th_a        delegate_loop ] next block time: 20140608T151245  interval: 15 seconds  now: 20140608T150819             $
501400ms       th_a        delegate_loop ] next block time: 20140608T151245  interval: 15 seconds  now: 20140608T150821             $
503401ms       th_a        delegate_loop ] next block time: 20140608T151245  interval: 15 seconds  now: 20140608T150823             $
504243ms       th_a              ~client ] waiting for delegate loop to complete                        client.cpp:350
505406ms       th_a          accept_loop ] fatal: error opening socket for rpc connection: 9
Operation canceled
    {"message":"Operation canceled"}
    asio  asio.cpp:45 error_handler
Unable to accept connection on socket.
    {}
    th_a  tcp_socket.cpp:212 accept                     node.cpp:1987
505406ms       th_a           ~node_impl ] unexpected exception on close 9
Operation canceled
    {"message":"Operation canceled"}
    asio  asio.cpp:45 error_handler
Unable to accept connection on socket.
    {}
    th_a  tcp_socket.cpp:212 accept                     node.cpp:586

Title: Re: Initial delegates, let's get ready!
Post by: wackou on June 08, 2014, 03:59:10 pm
VPS hosted at gandi.net
Location: Paris, France

Config (easily upgradable if necessary):
CPU: 2-core Xeon E5-2650L
RAM: 1G
BW: 100MB/s
OS: Debian stable + some libs from testing

Public keys:
wackou-delegate-1 XTS8Nycs16hWgGQTykcZ8n581scfBePSvyrxAWtfoLYBp4m6VqcCg
wackou-delegate-2 XTS5GfSidYreeUq4WCSEiEoFnmmCgJkDnGaXkPQDVPQJsrztKyCq3
wackou-delegate-3 XTS6sfrKvzeeo6P1Cz2eKusMRPEdWJhSYazJiikaXUizCd5o38oc5
wackou-delegate-4 XTS71xQ7RSg6w3Vbexe8gsQ27stzchhT9qR3o7PABF93rNn4zvJE2
wackou-delegate-5 XTS665TbeRTytMe8u3PusSPeUNUcdMDFke5g459NTU3RWfneafEWA
Title: Re: Initial delegates, let's get ready!
Post by: alexxy on June 08, 2014, 04:28:51 pm
BTW does current test net running? If so can someone send some funds to XTS5tpKsP27w6MtbxwYTb5qTRVfDEE9YvRFqPQjWn3FmPAuCP48iM
Thx!
Title: Re: Initial delegates, let's get ready!
Post by: valzav on June 08, 2014, 04:40:01 pm
DigitalOcean 2GB RAM / 40GB HDD Ubuntu 14.04 instance
Location: NYC

valzav-delegate-1  XTS5E3FBZW62UtqndRGog4zd1XMxjjYH2TSWVEQMVur2DiUXCPNJA
valzav-delegate-2  XTS7RUDKqo5hTnNR4BwZ46yGnhtVkLDdSNehgHba1hiauWuimbKhY
valzav-delegate-3  XTS7XGdLHxgvpLCXn2sAuN7bb8xQmyfLebpBtgmodRtN8tzg33CJQ
valzav-delegate-4  XTS6RamzeetCKiSowD8Q9K3VM4V5LtxKWhpJfDL4wPhxwszsoYdkE
valzav-delegate-5  XTS5t4KD3f1WioshQ7jpc2GzqgzFor7ub8GurtqpaYMsY4KkioCDu




Title: Re: Initial delegates, let's get ready!
Post by: Xeldal on June 08, 2014, 04:49:05 pm
I've got a node up on DO and created 5 keys.

How do I register as a Delegate?

How do I find what my name is / change my name to something other than delegateN?

How do I know my node is actually doing anything?


Edit:
"network_num_connections": 0,    <--I assume this means I'm not doing it right?
Title: Re: Initial delegates, let's get ready!
Post by: Harvey on June 08, 2014, 04:57:33 pm
DigitalOcean 2GB RAM / 40GB HDD
Ubuntu 14.04
Location: Singapore1

harvey-delegate-1: XTS7Bsi43JASDcPdgcLaXSLQ7mVNJReUvG4rcQYHHaJ3Ca7SLPYyq
harvey-delegate-2: XTS7qQScYbuFqsffgH6AammYXWMkZ9jSYdsYW21zguc2k2N3hYnfN
harvey-delegate-3: XTS6LDMYp9UNEYLUEdpCqx5dCEkWwrpP67LE5Zu3sSYqjP6LraqTW
harvey-delegate-4: XTS7fzyfX657vDUP4UVXRHNxCMZsGpCCGkvP7rN5NKkuEjktg5sHd
harvey-delegate-5: XTS7ze619FTgRReQsYEKYj8CbuiWB17q629gCz34Q7aeqe4yMida5
Title: Re: Initial delegates, let's get ready!
Post by: bitcoinerS on June 08, 2014, 06:37:09 pm
For those of you having build issues.   I had similar looking errors (i didn't copy them) when attempting to build on a vm with less than 2gb of ram.   Try increasing ram to 2gb and build again.   If that doesn't work you will have to wait for the experts.

I increased ram to 2 GB and tried again.

Code: [Select]
VERBOSE=1 make
...

[ 72%] Generating include/bts/api/common_api.hpp, ../rpc_stubs/common_api_rpc_server.cpp, ../rpc_stubs/common_api_rpc_client.cpp, ../rpc_stubs/common_api_client.cpp, ../rpc_stubs/include/bts/rpc_stubs/common_api_rpc_server.hpp, ../rpc_stubs/include/bts/rpc_stubs/common_api_rpc_client.hpp, ../rpc_stubs/include/bts/rpc_stubs/common_api_client.hpp, ../rpc_stubs/include/bts/rpc_stubs/common_api_overrides.ipp
cd /root/bitshares_toolkit/libraries/api && ./bts_api_generator --api-classname=common_api --api-interface-output-dir=/root/bitshares_toolkit/libraries/api --rpc-stub-output-dir=/root/bitshares_toolkit/libraries/rpc_stubs /root/bitshares_toolkit/libraries/api/types.json /root/bitshares_toolkit/libraries/api/blockchain_api.json /root/bitshares_toolkit/libraries/api/wallet_api.json /root/bitshares_toolkit/libraries/api/network_api.json /root/bitshares_toolkit/libraries/api/bitcoin_api.json /root/bitshares_toolkit/libraries/api/general_api.json
terminate called after throwing an instance of 'std::runtime_error'
  what():  locale::facet::_S_create_c_locale name not valid
Aborted
make[2]: *** [libraries/api/include/bts/api/common_api.hpp] Error 134
make[2]: Leaving directory `/root/bitshares_toolkit'
make[1]: *** [libraries/api/CMakeFiles/bts_api.dir/all] Error 2
make[1]: Leaving directory `/root/bitshares_toolkit'
make: *** [all] Error 2

Title: Re: Initial delegates, let's get ready!
Post by: bitcoinerS on June 08, 2014, 07:10:41 pm
I am trying to initialize my AGS based shares from PTS wallet and blockchain Bitcoin wallet.


Title: Re: Initial delegates, let's get ready!
Post by: muse-umum on June 08, 2014, 07:12:05 pm
2 Cores  2GB RAM  48GB SSD
Ubuntu 14.04                                   
Tokyo, Japan
                 
Code: [Select]
heyd-delegate-1                       XTS5Q7j3ZAYwjGAuK6AfWiqDuahnah9MVHXxGAr8yjsxWwuEAX9xg
heyd-delegate-2                       XTS5K6TmQjqReTUhWMg3EBjQ26VB6r26jMn4r2VEG2ykWh2xFkUpP
heyd-delegate-3                       XTS5HHx85ASdW3b4UmyV8g2rLyYRfHeTj8aH6E1DTE11jFUBr96as
heyd-delegate-4                       XTS7UUQZfy1hrUwgsEogy7GsjPq97EHjok5gUEav2bTaDTdBTQtNP
heyd-delegate-5                       XTS7Gv5RbxdSCT8T84Q2L3owbrRJUFQBtMgRU3De1GAHYggyQjbZQ     
Title: Re: Initial delegates, let's get ready!
Post by: toast on June 08, 2014, 07:14:13 pm
svk-delegate-1: XTSPC2qa4snEatrz7coSLMsyHdH8n2uaQLsz
svk-delegate-2: XTS8WCd3V4QRsWW79J9SbGHWkZZrZpVskSpc
svk-delegate-3: XTS9bAPKsBQT2NHoADqxQHFAr7v1QQNDne5J
svk-delegate-4: XTSBbGnohrKfS214De29gcc9m28cUMcBTLP
svk-delegate-5: XTS9Ez7UASJsY7LZfDmZxyoJFGzStjxv9s65

Location: France
Ubuntu 14.04 VM
i3 2.1 2gb RAM
SSD
1GB Fiber Internet

Those are your addresses, we need your public keys. (The longer one thta starts with XTS...)
Title: Re: Initial delegates, let's get ready!
Post by: Xeldal on June 08, 2014, 07:18:34 pm
For anyone else who can't find any clear directions, and is fumbling around like i am trying to figure it out.

For a ubuntu node.
Once I launched my node via these instructions: https://github.com/BitShares/bitshares_toolkit/blob/master/BUILD_UBUNTU.md

I navigate to bitshares_toolkit/programs/utils/
I then launch bts_create_key   with the command ./bts_create_key
I do this 5 times to get 5 keys

I navigate to /bitshares_toolkit/programs/client directory
I then launch bitshares_client   with the command ./bitshares_client

This launches the client.  You can then type help here for a list of commands.

I then try to load the delegate key into a wallet as per Toast directions with:
wallet_add_contact_account Xeldal-1 XTS5iNWht2kEmdWNDf6cRz6HiVEs2zk3X61GpQvrQT1wQf66xucit

but I get an error:
Code: [Select]
A wallet must be open to execute this command. You can:
(o) Open an existing wallet
(c) Create a new wallet
(q) Abort command
I don't have a wallet yet evidently so I select the second option 'c' Create new wallet
I pick a name and then a password

I then retry with Toast directions:
wallet_add_contact_account Xeldal-1 XTS5iNWht2kEmdWNDf6cRz6HiVEs2zk3X61GpQvrQT1wQf66xucit
and
wallet_import_private_key 5xxxxxxxWIF-Private-Key-Herexxxxxxxxxxx Xeldal-1

This seems to work.

I don't know if I've done any of this correctly as I'm unable to find any clear directions.
Some feedback or a link to these elusive directions I'm missing would be appreciated.

Thanks.
Title: Re: Initial delegates, let's get ready!
Post by: toast on June 08, 2014, 07:24:18 pm

I then retry with Toast directions:
wallet_add_contact_account Xeldal-1 XTS5iNWht2kEmdWNDf6cRz6HiVEs2zk3X61GpQvrQT1wQf66xucit
and
wallet_import_private_key 5xxxxxxxWIF-Private-Key-Herexxxxxxxxxxx Xeldal-1

This seems to work.


You are adding a contact account, but you should add a "receive" account with "wallet_account_create".

We will provide much clearer instructions shortly.
Title: Re: Initial delegates, let's get ready!
Post by: toast on June 08, 2014, 07:25:26 pm
How do i leave wallet unlocked and opened when i close putty/console window?  Everything just shuts down then. I'm using ubuntu:-[

ctrl+z  suspend job
bg <jobnum (usually 1)>
disown %<jobnum>
Title: Re: Initial delegates, let's get ready!
Post by: toast on June 08, 2014, 07:26:11 pm
We've picked the delegate list. Stay tuned for detailed instructions for the real dry run.

Will make a separate tech support thread too.
Title: Re: Initial delegates, let's get ready!
Post by: bytemaster on June 08, 2014, 07:37:06 pm
For those of you having build issues.   I had similar looking errors (i didn't copy them) when attempting to build on a vm with less than 2gb of ram.   Try increasing ram to 2gb and build again.   If that doesn't work you will have to wait for the experts.

I increased ram to 2 GB and tried again.

Code: [Select]
VERBOSE=1 make
...

[ 72%] Generating include/bts/api/common_api.hpp, ../rpc_stubs/common_api_rpc_server.cpp, ../rpc_stubs/common_api_rpc_client.cpp, ../rpc_stubs/common_api_client.cpp, ../rpc_stubs/include/bts/rpc_stubs/common_api_rpc_server.hpp, ../rpc_stubs/include/bts/rpc_stubs/common_api_rpc_client.hpp, ../rpc_stubs/include/bts/rpc_stubs/common_api_client.hpp, ../rpc_stubs/include/bts/rpc_stubs/common_api_overrides.ipp
cd /root/bitshares_toolkit/libraries/api && ./bts_api_generator --api-classname=common_api --api-interface-output-dir=/root/bitshares_toolkit/libraries/api --rpc-stub-output-dir=/root/bitshares_toolkit/libraries/rpc_stubs /root/bitshares_toolkit/libraries/api/types.json /root/bitshares_toolkit/libraries/api/blockchain_api.json /root/bitshares_toolkit/libraries/api/wallet_api.json /root/bitshares_toolkit/libraries/api/network_api.json /root/bitshares_toolkit/libraries/api/bitcoin_api.json /root/bitshares_toolkit/libraries/api/general_api.json
terminate called after throwing an instance of 'std::runtime_error'
  what():  locale::facet::_S_create_c_locale name not valid
Aborted
make[2]: *** [libraries/api/include/bts/api/common_api.hpp] Error 134
make[2]: Leaving directory `/root/bitshares_toolkit'
make[1]: *** [libraries/api/CMakeFiles/bts_api.dir/all] Error 2
make[1]: Leaving directory `/root/bitshares_toolkit'
make: *** [all] Error 2


I have seen this error before on some linux systems, I will look into a fix.
Title: Re: Initial delegates, let's get ready!
Post by: bytemaster on June 08, 2014, 07:38:42 pm
How do i leave wallet unlocked and opened when i close putty/console window?  Everything just shuts down then. I'm using ubuntu:-[

ctrl+z  suspend job
bg <jobnum (usually 1)>
disown %<jobnum>

I would highly recommend running your delegate via screen and GDB.   I will get Toast to post instructions on how to do this.   This way if your delegate crashes then you can give us a meaningful stack trace and you can also have interactive console commands to manipulate it.
Title: Re: Initial delegates, let's get ready!
Post by: bytemaster on June 08, 2014, 07:40:02 pm
For anyone else who can't find any clear directions, and is fumbling around like i am trying to figure it out.

For a ubuntu node.
Once I launched my node via these instructions: https://github.com/BitShares/bitshares_toolkit/blob/master/BUILD_UBUNTU.md

I navigate to bitshares_toolkit/programs/utils/
I then launch bts_create_key   with the command ./bts_create_key
I do this 5 times to get 5 keys

I navigate to /bitshares_toolkit/programs/client directory
I then launch bitshares_client   with the command ./bitshares_client

This launches the client.  You can then type help here for a list of commands.

I then try to load the delegate key into a wallet as per Toast directions with:
wallet_add_contact_account Xeldal-1 XTS5iNWht2kEmdWNDf6cRz6HiVEs2zk3X61GpQvrQT1wQf66xucit

but I get an error:
Code: [Select]
A wallet must be open to execute this command. You can:
(o) Open an existing wallet
(c) Create a new wallet
(q) Abort command
I don't have a wallet yet evidently so I select the second option 'c' Create new wallet
I pick a name and then a password

I then retry with Toast directions:
wallet_add_contact_account Xeldal-1 XTS5iNWht2kEmdWNDf6cRz6HiVEs2zk3X61GpQvrQT1wQf66xucit
and
wallet_import_private_key 5xxxxxxxWIF-Private-Key-Herexxxxxxxxxxx Xeldal-1

This seems to work.

I don't know if I've done any of this correctly as I'm unable to find any clear directions.
Some feedback or a link to these elusive directions I'm missing would be appreciated.

Thanks.

Thanks for posting these clear directions.... I will be writing many directions today and posting them at bitshares.org/documenation and linking to it from here.