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
16
General Discussion / Re: BTS X is Live
« on: July 20, 2014, 11:50:26 pm »
Maybe it's already been asked (but the forum search didn't turn anything up), but why is it that when doing

Code: [Select]
blockchain_list_assets
and again after 10 secondes.
the supply of BTSX is going up with about 0.6BTSX/block?

I thought I would see it slowly declining because of the transaction fee burning.

@delulo 4 GB swap should probably be sufficient, if not, trial and error...

17
BitShares AGS / Re: No AGS for my BTC, am I overlooking something?
« on: July 20, 2014, 11:19:44 pm »
The tool does give my address a balance

0.001% of the ags allocation (200 total 50% ags 50% btc, +- 0.001 balance on that address).

So it looks like everything is alright and agsexplorer is bugged?

18
General Discussion / Re: BTS X is Live
« on: July 20, 2014, 03:00:07 pm »
Are those init* delegates going to be gradually replaced by actual delegates from around the world?

Right now it's kind of hard to push your delegate up, when EACH (!!!) init* delegate has over 3% of total votes...

And init* delegates create majority of active ones.

BTW: From my perspective it looks like if someone has, say, 3.9% of all shares, and creates 101 delegates all of which he approves, then each and every delegate gets 3.9% Approval. This makes a total of over 390% and effectively blocks others from becoming a delegate.
Shouldn't instead those 3.9% of all votes be divided equally amongst those delegates user approved, so that total # of votes for all approved delegates makes sum of 3.9%?

It is my understanding that the 3.9% stake gets divided over everyone you vote on. So if you have 10% stake, and you voted for 100 delegates then your 10% gets divided over 100, meaning 0.1%/delegate.

can bytemaster confirm that?

the system uses approval voting. your votes are not divided. if you vote for 100 delegates then each delegates gets 10% approval. as the network matures and more people claim their stake delegates will have to maintain approval much higher than the 3.9%

Alright, sorry for the confusion caused.

19
General Discussion / Re: BTS X is Live
« on: July 20, 2014, 01:13:37 pm »
Are those init* delegates going to be gradually replaced by actual delegates from around the world?

Right now it's kind of hard to push your delegate up, when EACH (!!!) init* delegate has over 3% of total votes...

And init* delegates create majority of active ones.

BTW: From my perspective it looks like if someone has, say, 3.9% of all shares, and creates 101 delegates all of which he approves, then each and every delegate gets 3.9% Approval. This makes a total of over 390% and effectively blocks others from becoming a delegate.
Shouldn't instead those 3.9% of all votes be divided equally amongst those delegates user approved, so that total # of votes for all approved delegates makes sum of 3.9%?

It is my understanding that the 3.9% stake gets divided over everyone you vote on. So if you have 10% stake, and you voted for 100 delegates then your 10% gets divided over 100, meaning 0.1%/delegate.

20
BitShares AGS / No AGS for my BTC, am I overlooking something?
« on: July 20, 2014, 12:20:01 pm »
http://www1.agsexplorer.com/balances/1KrtvvJ4KhhQXLqyQXkgvQ3CApKmHbyg9t
http://www1.agsexplorer.com/by_date/2014-3-3

0.1 to ANGEL BTC address on 03-03-14.

A donation made with the same timestamp: http://www1.agsexplorer.com/balances/1Dy8TtQvc9W7WqdowN4avVtnLDu3VLJch9

What can I do to resolve this?

Thanks in advance

21
General Discussion / Re: Dry Run 2: The Real Deal
« on: June 19, 2014, 04:23:28 pm »

In an attempt to simplify concepts we have decided to NOT overload the term 'address' as used in bitcoin.

Accounts have Public Keys which we are calling your Account Key and contain automatically generated addresses from TITAN or from imported bitcoin wallets.
An address is the hash of a public key used to control a balance (spendable entry in the blockchain).

Our goal is that users never have to think much about their Account Keys and NEVER about their addresses.

https://github.com/BitShares/bitshares_toolkit/wiki/Wallets,-accounts,-owner-&-active-keys,-addresses---The-differences-between-Bitcoin-and-Bitshares

22
General Discussion / Re: Dry Run 2: The Real Deal
« on: June 18, 2014, 08:43:09 am »

Is there any way we could get the wiki updated with the recently added debug commands? Like list_errors and max_connections and all that? That way those of us who came a little late can be more helpful.


Sent from my iPhone using Tapatalk

https://github.com/BitShares/bitshares_toolkit/wiki should be done. Generated with the api json documents.

Created a pull request: https://github.com/BitShares/bitshares_toolkit/pull/332
Manually fixed the JSON.

23
General Discussion / Re: Dry Run 2: The Real Deal
« on: June 17, 2014, 05:37:52 pm »
Switched to a manually compiled/installed version of readline (coming from macports readline @6.3.003_0) and it built successfully.

Also discovered why the JSON RPC API didn't work at first, there is another difference between the bitcoin RPC and bitshares RPC.
Bitcoin RPC doesn't require to be passed an "id", bitshares RPC does.

http://<user>:<pass>@localhost:<httprpcport>/rpc and send an "id" and it should work (like so: "id" : uniqueidentifier)

24
General Discussion / Re: Dry Run 2: The Real Deal
« on: June 17, 2014, 05:00:05 pm »
Repost:

Code: [Select]
In file included from /Users/maurits/bitsharesxts/bitshares_toolkit/libraries/db/include/bts/db/level_map.hpp:14:
In file included from /Users/maurits/bitsharesxts/bitshares_toolkit/libraries/db/include/bts/db/upgrade_leveldb.hpp:9:
In file included from /opt/local/include/boost/regex.hpp:31:
In file included from /opt/local/include/boost/regex/v4/regex.hpp:48:
/opt/local/include/boost/regex/v4/regex_raw_buffer.hpp:132:7: warning: 'register' storage class specifier is deprecated [-Wdeprecated-register]
      register pointer result = end;
      ^~~~~~~~~
1 warning generated.
Linking CXX executable bitshares_client
Undefined symbols for architecture x86_64:
  "_rl_copy_text", referenced from:
      bts::cli::detail::cli_impl::display_status_message(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&) in libbts_cli.a(cli.cpp.o)
  "_rl_getc", referenced from:
      fc::detail::functor_run<bts::cli::detail::get_character::$_0>::run(void*, void*) in libbts_cli.a(cli.cpp.o)
  "_rl_replace_line", referenced from:
      bts::cli::detail::cli_impl::display_status_message(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&) in libbts_cli.a(cli.cpp.o)
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make[2]: *** [programs/client/bitshares_client] Error 1
make[1]: *** [programs/client/CMakeFiles/bitshares_client.dir/all] Error 2
make: *** [all] Error 2

Is there a configuration error on my part? (Mac OS X 10.9)

Remove your cmake cache... it looks like you compiled / installed the latest readline but cmake is still linking to the old one. 

rm CMakeCache.txt

I do
Code: [Select]
rm -rf bitshares_toolkit every time when I want to update/rebuild bitshares_toolkit.

ran:

Code: [Select]
rm CMakeCache.txt
Code: [Select]
cmake -DCMAKE_PREFIX_PATH=/usr/local/ssl .
Code: [Select]
make
And I got the same error.

25
General Discussion / Re: Dry Run 2: The Real Deal
« on: June 17, 2014, 04:36:48 pm »
Repost:

Code: [Select]
In file included from /Users/maurits/bitsharesxts/bitshares_toolkit/libraries/db/include/bts/db/level_map.hpp:14:
In file included from /Users/maurits/bitsharesxts/bitshares_toolkit/libraries/db/include/bts/db/upgrade_leveldb.hpp:9:
In file included from /opt/local/include/boost/regex.hpp:31:
In file included from /opt/local/include/boost/regex/v4/regex.hpp:48:
/opt/local/include/boost/regex/v4/regex_raw_buffer.hpp:132:7: warning: 'register' storage class specifier is deprecated [-Wdeprecated-register]
      register pointer result = end;
      ^~~~~~~~~
1 warning generated.
Linking CXX executable bitshares_client
Undefined symbols for architecture x86_64:
  "_rl_copy_text", referenced from:
      bts::cli::detail::cli_impl::display_status_message(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&) in libbts_cli.a(cli.cpp.o)
  "_rl_getc", referenced from:
      fc::detail::functor_run<bts::cli::detail::get_character::$_0>::run(void*, void*) in libbts_cli.a(cli.cpp.o)
  "_rl_replace_line", referenced from:
      bts::cli::detail::cli_impl::display_status_message(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&) in libbts_cli.a(cli.cpp.o)
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make[2]: *** [programs/client/bitshares_client] Error 1
make[1]: *** [programs/client/CMakeFiles/bitshares_client.dir/all] Error 2
make: *** [all] Error 2

Is there a configuration error on my part? (Mac OS X 10.9)

26
General Discussion / Re: Dry Run 2: The Real Deal
« on: June 17, 2014, 03:32:37 pm »
Build failed:
Code: [Select]
1 warning generated.
Linking CXX executable bitshares_client
Undefined symbols for architecture x86_64:
  "_rl_copy_text", referenced from:
      bts::cli::detail::cli_impl::display_status_message(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&) in libbts_cli.a(cli.cpp.o)
  "_rl_getc", referenced from:
      fc::detail::functor_run<bts::cli::detail::get_character::$_0>::run(void*, void*) in libbts_cli.a(cli.cpp.o)
  "_rl_replace_line", referenced from:
      bts::cli::detail::cli_impl::display_status_message(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&) in libbts_cli.a(cli.cpp.o)
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make[2]: *** [programs/client/bitshares_client] Error 1
make[1]: *** [programs/client/CMakeFiles/bitshares_client.dir/all] Error 2
make: *** [all] Error 2

27
General Discussion / Re: Dry Run 2: The Real Deal
« on: June 16, 2014, 08:23:45 am »
who can send me some XTS or LOVE to test?
thanks
I have registe the wallet account alt.

Sent.

28
General Discussion / Re: Dry Run 2: The Real Deal
« on: June 16, 2014, 07:38:01 am »
Can someone send me some test fund for applying delegate?

XTS8Eso3RfRDQviSKuQxhWL9hQCQ7siaZPbDzYULxcat1d1ncdhu1

My node is up and running with average 14 connections.  You are welcome to connect to it.

180.153.142.120:8764
sent

How did you do that? wallet_transfer seems to only work with account names, or did you use his account name?

29
General Discussion / Re: Dry Run 2: The Real Deal
« on: June 15, 2014, 12:05:05 pm »
I would like to get voted in, I would appreciate it if someone votes for me:

Code: [Select]
wallet_set_delegate_trust_level mauritso 1
If I am a delegate at the start of the XTS network I will launch a Amazon EC2 instance (m1.small/m3.medium/m3.large depending on the requirements in a location of your choosing) and keep it running for at least a month. After my amazon credit is gone, I am still a delegate and it got enough money in transaction fees I will probably switch to a dedicated host.

30
General Discussion / Re: Dry Run 2: The Real Deal
« on: June 14, 2014, 10:16:02 pm »
Resync your blockchain

Thanks, normally I remove the datadir, but this time I had a wallet in which I imported all my keys and stuff. Need to adapt my rebuild script to leave the config.json and the wallet dir.

after a while:

Code: [Select]
Current executable set to './bitshares_client' (x86_64).
(lldb) run
Process 59989 launched: './bitshares_client' (x86_64)
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"
Not starting RPC server, use --server to enable the RPC interface
Listening for P2P connections on port 58343
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
Process 59989 stopped
* thread #1: tid = 0x26f60e, 0x000000010056a97d bitshares_client`EVP_EncryptUpdate + 29, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS (code=1, address=0x0)
    frame #0: 0x000000010056a97d bitshares_client`EVP_EncryptUpdate + 29
bitshares_client`EVP_EncryptUpdate + 29:
-> 0x10056a97d:  movq   (%r12), %rbx
   0x10056a981:  testb  $0x10, 0x12(%rbx)
   0x10056a985:  je     0x10056a9ad               ; EVP_EncryptUpdate + 77
   0x10056a987:  movq   %rdx, %r14

Pages: 1 [2] 3 4 5