Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - mauritso

Pages: 1 2 [3] 4 5
31
General Discussion / Re: Dry Run 2: The Real Deal
« on: June 14, 2014, 09:54:54 pm »
Same here:

Code: [Select]
Logging to file "/Users/maurits/Library/Application Support/BitSharesXTS/default.log"
Logging RPC to file "/Users/maurits/Library/Application Support/BitSharesXTS/rpc.log"
Loading config "/Users/maurits/Library/Application Support/BitSharesXTS/config.json"
{
  "rpc": {
    "rpc_user": "user",
    "rpc_password": "pass",
    "rpc_endpoint": "127.0.0.1:5681",
    "httpd_endpoint": "127.0.0.1:5680",
    "htdocs": "/Users/maurits/bitsharesxts/web_wallet/generated"
  },
  "default_peers": [
    "107.170.30.182:8764",
    "114.215.104.153:8764",
    "84.238.140.192:8764"
  ],
  "ignore_console": false,
  "logging": {
    "includes": [],
    "appenders": [],
    "loggers": []
  }
}
Loading blockchain from "/Users/maurits/Library/Application Support/BitSharesXTS/chain"
Starting JSON RPC server on port 5681 (localhost only)
Starting HTTP JSON RPC server on port 5680 (localhost only)
------------ error --------------
8 out_of_range_exception: Out of Range
read datastream of length 23 over by 1
    {"method":"read","len":23,"over":1}
    th_a  datastream.cpp:6 throw_datastream_range_error
error unpacking uint8_t
    {"type":"uint8_t"}
    th_a  raw.hpp:440 unpack
optional<fc::exception>
    {"type":"fc::exception"}
    th_a  raw.hpp:164 unpack
Error unpacking field last_error
    {"field":"last_error"}
    th_a  raw.hpp:222 operator()
error unpacking bts::net::potential_peer_record
    {"type":"bts::net::potential_peer_record"}
    th_a  raw.hpp:440 unpack

32
General Discussion / Re: Dry Run 2: The Real Deal
« on: June 14, 2014, 05:08:16 pm »
@spartako will you be able to send some funds to me too (enough to register as a delegate would be awesome)? Thanks in advance.

Code: [Select]
XTS6sWfWBPSxbYKuxaL7isG87w1YSdvJg6dj1J5qhzzPvYmyVTAFg
How did you get funds? I tried some ways to import my keys, but failed, haven't tried since. If you imported your keys, can you please describe how?

I sent you 10 XTS, I think it is enough to become delegate
Code: [Select]
3802.0    2014-06-14T14:10:00 spartako            mauritso                                                      10.000000 XTS        0.010000 XTS        f9a2195e

I imported my private keys with the command :
Code: [Select]
wallet_import_private_key <BITCOIN_PRIVATEKEY> spartako

What error do you get?

Thank you, I will vote for you if it helps (smart way of buying votes ;)

I will try to import my private keys once again, I will post here if it works or not in a moment.

EDIT: It worked, tried the same thing a few days back, it didn't work that time.

33
General Discussion / Re: Dry Run 2: The Real Deal
« on: June 14, 2014, 02:07:22 pm »
@spartako will you be able to send some funds to me too (enough to register as a delegate would be awesome)? Thanks in advance.

Code: [Select]
XTS6sWfWBPSxbYKuxaL7isG87w1YSdvJg6dj1J5qhzzPvYmyVTAFg
How did you get funds? I tried some ways to import my keys, but failed, haven't tried since. If you imported your keys, can you please describe how?

34
General Discussion / Re: Delegates, start your engines!
« on: June 12, 2014, 11:51:42 am »
Code: [Select]
Scanning dependencies of target dev_tests
[ 98%] Building CXX object tests/CMakeFiles/dev_tests.dir/dev_tests.cpp.o
/Users/maurits/bitsharesxts/bitshares_toolkit/tests/dev_tests.cpp:3:10: fatal error: 'dev_fixture.hpp' file not found
#include "dev_fixture.hpp"
         ^
1 error generated.
make[2]: *** [tests/CMakeFiles/dev_tests.dir/dev_tests.cpp.o] Error 1
make[1]: *** [tests/CMakeFiles/dev_tests.dir/all] Error 2
make: *** [all] Error 2

Same here.

35
General Discussion / Re: Delegates, start your engines!
« on: June 11, 2014, 08:33:10 pm »
fresh build and now i can't find ./bitshares_client

Code: [Select]
root@we:~/bitshares_toolkit# gdb ./bitshares_client
GNU gdb (Ubuntu 7.7-0ubuntu3.1) 7.7
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
./bitshares_client: No such file or directory.
(gdb) run
Starting program:
No executable file specified.
Use the "file" or "exec-file" command.

The client is in ~/bitshares_toolkit/programs/client/

gdb ~/bitshares_toolkit/programs/client/bitshares_client

36
General Discussion / Re: Delegates, start your engines!
« on: June 10, 2014, 04:28:13 pm »
https://dl.dropboxusercontent.com/u/26420542/outputcmakemakeOSX10.9.txt

Code: [Select]
[ 99%] Built target key_to_wif
Scanning dependencies of target wallet_tests
[100%] Building CXX object tests/CMakeFiles/wallet_tests.dir/wallet_tests.cpp.o
/Users/maurits/bitsharesxts/bitshares_toolkit/tests/wallet_tests.cpp:210:17: error: implicit instantiation of undefined template 'std::__1::basic_ifstream<char, std::__1::char_traits<char> >'
  std::ifstream lhs(_result_file.string());
                ^
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../lib/c++/v1/iosfwd:131:33: note: template is declared here
    class _LIBCPP_TYPE_VIS_ONLY basic_ifstream;
                                ^
/Users/maurits/bitsharesxts/bitshares_toolkit/tests/wallet_tests.cpp:211:17: error: implicit instantiation of undefined template 'std::__1::basic_ifstream<char, std::__1::char_traits<char> >'
  std::ifstream rhs(_expected_result_file.string());
                ^
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../lib/c++/v1/iosfwd:131:33: note: template is declared here
    class _LIBCPP_TYPE_VIS_ONLY basic_ifstream;
                                ^
/Users/maurits/bitsharesxts/bitshares_toolkit/tests/wallet_tests.cpp:320:19: error: implicit instantiation of undefined template 'std::__1::basic_ifstream<char, std::__1::char_traits<char> >'
    std::ifstream test_config_file("test.config");
                  ^
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../lib/c++/v1/iosfwd:131:33: note: template is declared here
    class _LIBCPP_TYPE_VIS_ONLY basic_ifstream;
                                ^
/Users/maurits/bitsharesxts/bitshares_toolkit/tests/wallet_tests.cpp:333:21: error: use of undeclared identifier 'CommandLineToArgvA'
      char** argv = CommandLineToArgvA(line.c_str(),&argc);
                    ^
fatal error: too many errors emitted, stopping now [-ferror-limit=]
5 errors generated.
make[2]: *** [tests/CMakeFiles/wallet_tests.dir/wallet_tests.cpp.o] Error 1
make[1]: *** [tests/CMakeFiles/wallet_tests.dir/all] Error 2
make: *** [all] Error 2


Build was indeed broken, trying again now. still broken it seems.
Posting the log just in case. Mac OS X 10.9.3.
430 warnings (a lot about deprecated functions, I know warnings don't mean that something is broken)

This happens with the most current version:

Code: [Select]
[100%] Building CXX object tests/CMakeFiles/wallet_tests.dir/wallet_tests.cpp.o
/Users/maurits/bitsharesxts/bitshares_toolkit/tests/wallet_tests.cpp:229:17: error: implicit instantiation of undefined template 'std::__1::basic_ifstream<char, std::__1::char_traits<char> >'
  std::ifstream lhs(_result_file.string().c_str());
                ^
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../lib/c++/v1/iosfwd:131:33: note: template is declared here
    class _LIBCPP_TYPE_VIS_ONLY basic_ifstream;
                                ^
/Users/maurits/bitsharesxts/bitshares_toolkit/tests/wallet_tests.cpp:230:17: error: implicit instantiation of undefined template 'std::__1::basic_ifstream<char, std::__1::char_traits<char> >'
  std::ifstream rhs(_expected_result_file.string().c_str());
                ^
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../lib/c++/v1/iosfwd:131:33: note: template is declared here
    class _LIBCPP_TYPE_VIS_ONLY basic_ifstream;
                                ^
/Users/maurits/bitsharesxts/bitshares_toolkit/tests/wallet_tests.cpp:339:19: error: implicit instantiation of undefined template 'std::__1::basic_ifstream<char, std::__1::char_traits<char> >'
    std::ifstream test_config_file("test.config");
                  ^
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../lib/c++/v1/iosfwd:131:33: note: template is declared here
    class _LIBCPP_TYPE_VIS_ONLY basic_ifstream;
                                ^
/Users/maurits/bitsharesxts/bitshares_toolkit/tests/wallet_tests.cpp:352:21: error: use of undeclared identifier 'CommandLineToArgvA'
      char** argv = CommandLineToArgvA(line.c_str(),&argc);
                    ^
fatal error: too many errors emitted, stopping now [-ferror-limit=]
5 errors generated.
make[2]: *** [tests/CMakeFiles/wallet_tests.dir/wallet_tests.cpp.o] Error 1
make[1]: *** [tests/CMakeFiles/wallet_tests.dir/all] Error 2
make: *** [all] Error 2

Same error as above, but other line numbers it seems.

37
General Discussion / Re: Delegates, start your engines!
« on: June 09, 2014, 08:32:06 am »
Create a wallet and import your keys:

Code: [Select]
(wallet closed) >>> wallet_create mywallet
passphrase:
passphrase (verify):
OK

mywallet (unlocked) >>> unlock 999999
passphrase:
OK

mywallet (unlocked) >>> wallet_import_private_key 5KdeCK6PcFuZqh9XBPBN2tYG2MsgXpYXG3vzPhLK1VA8ye6Ptwf
OK
(repeat for each key - some will fail as we did not include all 5 for everyone)
Code: [Select]
mywallet (unlocked) >>> wallet_rescan_blockchain
...
Scan complete.
OK

Just followed the instructions and "(repeat for each key - some will fail as we did not include all 5 for everyone)" implies that all your keys will fail if you are not an initial delegate.

38
General Discussion / Re: Delegates, start your engines!
« on: June 09, 2014, 08:17:03 am »
Also.  If there are any nix masters out there.  What is the purpose of splitting the screen -S and the running gdb?

It seems like I can get similar results from running
screen -S Bitshares ./bitshares_client
without the step of running gdb
from a theoretical viewpoint, I'd like to understand the difference.

**this is purely for my educational purposes, and is not at all important**

GDB is a debugger, if the client crashes for example GDB can give some meaningful info as to why that happened.

If all of my private keys give me:

Code: [Select]
10
registered_account:
    {}
    th_a  wallet.cpp:777 import_private_key

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

    {"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
mauritso (unlocked) >>>

That would mean that I am not an initial delegate right? (Is there a list somewhere?)

39
General Discussion / Re: Initial delegates, let's get ready!
« 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?

40
General Discussion / Re: Initial delegates, let's get ready!
« 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?

41
Marketplace / Re: Bitshares Faucet Request for Proposal [1000 PTS]
« on: June 08, 2014, 12:38:32 pm »
Just listened to today's mumble session that I've recorded this morning.

I like the referral program idea, I think it can be even more effective if combined with social media campaign.
Here is an example how it can look like:
When somebody fills up a form at Faucet he or she gets redirected to congratulation page, this page should have a clear message - "Share on social media (Twitter, FB) and get some more shares, also you friends would have an opportunity to receive extra shares". And there should be social media share buttons that takes directly to social networks share pages.

Or another variant, visitor can be required to login to Faucet via social network of his choice (this can also can be used to limit multiple signups from the same user instead of using phone number), after he signs up a popup dialog can ask for permission to post a story to his social network feed.

SMS or Social media account in that case.
I would also like to see the option to register your name for "free" (paid by the faucet), without SMS or a social media account, no initial balance, just free registration (to make it not that attractive to people trying to game the system while giving privacy minded people an option to register for free).

Please use the registered in the blockchain names as the basis for the refferal URLs, I think it is best to use the least possible amount of additional databases on top of the bitshares x blockchain.

42
Marketplace / Re: Bitshares Faucet Bounty [1000 PTS]
« on: June 07, 2014, 02:11:09 pm »
Haven't really gotten anywhere, stuck on the communicating with the API part.

I can get data from bitcoind (curl, php library and python library)
The web wallet (which works trough RPC) works
Parse error if it is a correct method (getinfo)
404 if it is an incorrect method (getinfod)

It's driving me a bit crazy at this point, it this the kind of question I can ask in technical support (on how to do this correctly)?

I think the URL you require is     IP:PORT/rpc

Bitcoin doesn't have the '/rpc' part.

http://user:pass@127.0.0.1:port/rpc

Is what I used, when I got there the error changed to parsing error and I consistently got a 404 when providing a not existing method.

Alright, got it, works with curl now (didn't before, even with /rpc), still don't know what caused it, but using the json http port of the bitshares client + a working web wallet (which is accessible on that port) + using curl seems to work. Still can't get anywhere with PHP but at least it works with curl.

Still can't get it to work with python/php. I think I"ll open a thread in technical support about this.

As I have not really gotten anything done and I was just trying to learn a tip would be nice but certainly not necessary.

43
Marketplace / Re: Bitshares Faucet Bounty [1000 PTS]
« on: June 07, 2014, 01:58:32 pm »
Haven't really gotten anywhere, stuck on the communicating with the API part.

I can get data from bitcoind (curl, php library and python library)
The web wallet (which works trough RPC) works
Parse error if it is a correct method (getinfo)
404 if it is an incorrect method (getinfod)

It's driving me a bit crazy at this point, it this the kind of question I can ask in technical support (on how to do this correctly)?

I think the URL you require is     IP:PORT/rpc

Bitcoin doesn't have the '/rpc' part.

http://user:pass@127.0.0.1:port/rpc

Is what I used, when I got there the error changed to parsing error and I consistently got a 404 when providing a not existing method.

44
Marketplace / Re: Bitshares Faucet Bounty [1000 PTS]
« on: June 07, 2014, 01:38:43 pm »
Haven't really gotten anywhere, stuck on the communicating with the API part.

I can get data from bitcoind (curl, php library and python library)
The web wallet (which works trough RPC) works
Parse error if it is a correct method (getinfo)
404 if it is an incorrect method (getinfod)

It's driving me a bit crazy at this point, it this the kind of question I can ask in technical support (on how to do this correctly)?


45
Marketplace / Re: Bitshares Faucet Bounty [1000 PTS]
« on: June 06, 2014, 10:35:42 pm »
I think I will start working on it after I got some sleep (~12 hours from now), given that there is no-one else who already started working and updated us by that time. If I start with creating functions for validation and calling the RPC API then it would be easy for other people to use.

Nice draft...

Just make sure that every 'form' also comes with a JSON-RPC API call that we can issue from the wallet GUI without having to use your website interface.

No captcha's. 



Thanks I guess, hope it can be of some use.


Pages: 1 2 [3] 4 5