1486
General Discussion / Re: Airdrop 100% profit to bitsharestalk.org (0904 300BTSX)
« on: September 08, 2014, 08:26:30 am »
btsx:pmc
Thanks again!
Thanks again!
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.
1487
General Discussion / Re: Linux QT wallet compilation issues
« on: September 04, 2014, 02:37:05 pm »
Did you "make buildweb" and did it succeed?
1488
General Discussion / Re: 0.4.11 Testers Wanted (not mandatory)
« on: September 03, 2014, 08:55:08 am »
Looks good so far... this is the first version that hasn't crashed on me soon after starting, and it's been running for hours now. :-)
1489
KeyID / Re: [DNS] test network for advanced users
« on: August 31, 2014, 10:37:58 am »
Still playing around... and got an assertion failure. I have to admit that I don't really know what I'm doing.
Tried to buy the domain "pc", a few minutes later I was trying to look it up:
Tried to buy the domain "pc", a few minutes later I was trying to look it up:
Code: [Select]
pc (unlocked) >>> dotp2p_info pc
null
pc (unlocked) >>> dotp2p_show pc
bitshares_client: /usr/include/fc/optional.hpp:197: T* fc::optional<T>::operator->() [with T = bts::blockchain::domain_record]: Assertion `_valid' failed.
Program received signal SIGABRT, Aborted.
0xb7fdd424 in __kernel_vsyscall ()
(gdb) bt
#0 0xb7fdd424 in __kernel_vsyscall ()
#1 0xb797c577 in __GI_raise (sig=sig@entry=6)
at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
#2 0xb797f9a3 in __GI_abort () at abort.c:89
#3 0xb79756c7 in __assert_fail_base (
fmt=0xb7ab38f4 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n",
assertion=assertion@entry=0x9406ea1 "_valid",
file=file@entry=0x9406e84 "/usr/include/fc/optional.hpp",
line=line@entry=197,
function=function@entry=0x940cfa0 <fc::optional<bts::blockchain::domain_record>::operator->()::__PRETTY_FUNCTION__> "T* fc::optional<T>::operator->() [with T = bts::blockchain::domain_record]") at assert.c:92
#4 0xb7975777 in __GI___assert_fail (assertion=0x9406ea1 "_valid",
file=0x9406e84 "/usr/include/fc/optional.hpp", line=197,
function=0x940cfa0 <fc::optional<bts::blockchain::domain_record>::operator->()::__PRETTY_FUNCTION__> "T* fc::optional<T>::operator->() [with T = bts::blockchain::domain_record]") at assert.c:101
#5 0x08b3d172 in fc::optional<bts::blockchain::domain_record>::operator->() ()
#6 0x08b193ff in bts::client::detail::client_impl::dotp2p_show(std::string const&) ()
#7 0x08ecd460 in bts::rpc_stubs::common_api_client::dotp2p_show(std::string const&) ()
#8 0x08dcf104 in bts::rpc_stubs::common_api_rpc_server::dotp2p_show_positional(std::shared_ptr<fc::rpc::json_connection> const&, std::vector<fc::variant, std::allocator<fc::variant> > const&) ()
#9 0x08e37ab6 in bts::rpc_stubs::common_api_rpc_server::direct_invoke_positional_method(std::string const&, std::vector<fc::variant, std::allocator<fc::variant---Type <return> to continue, or q <return> to quit---
> > const&) ()
#10 0x08c59435 in bts::rpc::detail::rpc_server_impl::dispatch_authenticated_method(bts::api::method_data const&, std::vector<fc::variant, std::allocator<fc::variant> > const&) ()
#11 0x08c59c7d in bts::rpc::detail::rpc_server_impl::direct_invoke_method(std::string const&, std::vector<fc::variant, std::allocator<fc::variant> > const&) ()
#12 0x08c4c339 in bts::rpc::rpc_server::direct_invoke_method(std::string const&, std::vector<fc::variant, std::allocator<fc::variant> > const&) ()
#13 0x08c7020a in bts::cli::detail::cli_impl::execute_command(std::string const&, std::vector<fc::variant, std::allocator<fc::variant> > const&) ()
#14 0x08c70158 in bts::cli::detail::cli_impl::execute_interactive_command(std::string const&, std::vector<fc::variant, std::allocator<fc::variant> > const&) ()
#15 0x08c69159 in bts::cli::cli::execute_interactive_command(std::string const&, std::vector<fc::variant, std::allocator<fc::variant> > const&) ()
#16 0x08c6ac54 in bts::cli::detail::cli_impl::parse_and_execute_interactive_command(std::string, std::shared_ptr<fc::istream>) ()
#17 0x08c6b926 in bts::cli::detail::cli_impl::execute_command_line(std::string const&) ()
#18 0x08c6765c in bts::cli::detail::cli_impl::process_commands(std::istream*)
()
#19 0x08c6a54d in bts::cli::detail::cli_impl::start() ()
#20 0x08c688ca in bts::cli::cli::start() ()
#21 0x08b28c5e in bts::client::detail::client_impl::start() ()
#22 0x08b0c514 in bts::client::client::start()::{lambda()#1}::operator()() const ()
#23 0x08b1c869 in fc::detail::void_functor_run<bts::client::client::start()::{lambda()#1}>::run(void*, fc::detail::void_functor_run<bts::client::client::start()---Type <return> to continue, or q <return> to quit---
::{lambda()#1}>) ()
#24 0x08bce997 in fc::task_base::run_impl() ()
#25 0x08bce94d in fc::task_base::run() ()
#26 0x08bc6cf9 in fc::thread_d::run_next_task() ()
#27 0x08bc7024 in fc::thread_d::process_tasks() ()
#28 0x08bc6885 in fc::thread_d::start_process_tasks(int) ()
#29 0xb7c85597 in make_fcontext ()
from /usr/lib/i386-linux-gnu/libboost_context.so.1.54.0
1490
KeyID / Re: [DNS] test network for advanced users
« on: August 30, 2014, 08:53:41 pm »
Some funds, please:
xts:pc:KEY5r26eCoK87PYMmVZuAyVisyj4MfUCVG49uLiRniR8NzGMvG6oT
Thanks!
xts:pc:KEY5r26eCoK87PYMmVZuAyVisyj4MfUCVG49uLiRniR8NzGMvG6oT
Thanks!
1491
General Discussion / Re: Delegates, please response to this thread if your delegate updated to 0.4.9
« on: August 29, 2014, 11:50:51 am »Quotebitsapphire (unlocked) >>>
Program received signal SIGSEGV, Segmentation fault.
0x000000000065e91b in fc::exception::to_detail_string (this=this@entry=0xa46a1c0, ll=..., ll@entry=...)
at /root/bitsharesx/libraries/fc/src/exception.cpp:144
144 ss << variant(my->_code).as_string() <<" " << my->_name << ": " <<my->_what<<"\n";
I've been getting loads of these since 0.4.8, see https://github.com/BitShares/bitshares_toolkit/issues/647#issuecomment-53440518
1492
Marketplace / Re: [200BTSX] tool to convert bitcoin public key into BTSX/PTS address
« on: August 28, 2014, 08:12:45 pm »You cannot "generate a pubkey from a bitcoin address" because the address is essentially a cryptographic hash of the pubkey. Cryptographic hashes are one way - it's easy to compute the hash for a key but close to impossible to find the key(s) generating a given hash.but there is no way to convert an address to a public key (address is hash of public key)Is it even possible to to register a btsx account using a pubkey generated from a bitcoin address .. so that the holder of the privkey (bitcoin) can import an account name I registered for him?
1493
KeyID / Re: [DNS] Launch Checklist
« on: August 25, 2014, 08:00:34 am »I generated a partial genesis block using this tool.
Question: If I put 5bn as the total supply and 40%/40%, what happens with the remaining 20%? Is there a balance where the rest is allocated, or does the total in the genesis block simply equal 4bn? Thanks.
The total will equal 4bn. (The actual total is also contained in the json generated by the tool, right at the end.)
1494
LottoShares / Re: Problem with client upgrade
« on: August 22, 2014, 08:39:03 am »
You must delete the old blockchain and re-download the new one.
0. Shut down the lottoshares client
1. Go to $HOME/.lottoshares (or its equivalent on windows, whatever that may be)
2. Back up everything, especially wallet.dat
3. Delete everything EXCEPT wallet.dat
4. Start lottoshares client
0. Shut down the lottoshares client
1. Go to $HOME/.lottoshares (or its equivalent on windows, whatever that may be)
2. Back up everything, especially wallet.dat
3. Delete everything EXCEPT wallet.dat
4. Start lottoshares client
1495
KeyID / Re: [DNS] Launch Checklist
« on: August 22, 2014, 08:33:45 am »* PTS/AGS snapshot + audit. The tool on bitshares.org breaks for dates later than the end of AGS, and I want an audit of this tool and any existing PTS snapshot tool anyway.If you mean this tool: http://bitshares.org/resources/genesis-blocks/
I've been running the alternate implementation at http://ptsags.quisquis.de/ since its creation in february, and I've been comparing my PTS/AGS snapshots with those from the above site every day. Both sites have (with a few exceptions that were quickly resolved) provided consistent results during these past 6 months. The only difference is the slightly different handling of rounding issues, resulting in AGS balances differing by a few satoshis.
I have adapted my genesis block generator after the end of AGS to always use the final AGS balance. I think the other tool could be easily fixed to do the same.
1496
BitShares PTS / Re: Bitshares PTS upgrade proposal
« on: August 20, 2014, 01:03:03 pm »If you have a reason to wait please share. I can tell you many reasons why waiting can hurt shareholders. The protocol is inefficient, insecure, unscalable, and has a broken diff. algorithm. What we have now is a leaky bucket (more like a bucket cracked down the middle), pouring thousands of dollars of our wealth into the hands of a few centralized miners in exchange for literally NOTHING.
I have given my reasons.
Despite its undeniable deficiencies, PTS has been working fine for more than 9 months now.
The difficulty algorithm and block reward were known from the start, and have changed only once in the beginning - there really is nothing to complain about now. Yes, miners are now receiving block rewards for little work - but they still receive fewer PTS for much more work than many of the miners that were active in the early days of PTS. Like me. So what are you complaining about?
And I don't buy the myth that some people are peddling here. The core DPOS functionality is absolutely functional and market-ready. BTSX is undeniable evidence of this fact. At this time it has a $21M market cap and is the 5th largest cryptocurrency on earth. If you consider that to be "premature" but feel comfortable with the broken status quo then your priorities are in a different place.
The BTS-X client has crashed several times on me. These crashes had to do with networking code, and with functions in the "fc" library. There are also numerous complaints in the forum. The client is seeing several updates peer week. To me, BTS-X provides undeniable evidence that the current DPOS implementation is immature.
Market cap is completely irrelevant - a 15 year old millionaire can't buy alcohol in the US.
PTS has never crashed on me. The difficulty adjustment sucks, but the client is stable and performs the job it was designed for quite well.
1497
BitShares PTS / Re: Bitshares PTS upgrade proposal
« on: August 19, 2014, 04:37:02 pm »original plan was to make new PTS (DPOS) based on BitShares Vote codebase, this is why until now we don't have any milestones and deadline, if you want to hear raw realistic estimation, end of October, but if you want to hear more detailed plan - you should wait until Vote will be released.
Sometimes pushing development and taking additional risk does not give expected advantages.
Glad to hear that
a) PTS will move to DPOS *eventually*, and
b) this is not rushed. I think it would be premature at this time.
1498
BitShares PTS / Re: PTS upgrade poll
« on: August 17, 2014, 08:31:10 am »DPOS is not unstable. Stability issues in an old version of the Ubuntu client do not mean it is unstable.
Clarification: the "old version" was the newest official version at the time of my tests.
If stability issues in an official version do not mean it is unstable, then what else does?
Testz is the custodian of Bitshares PTS and is tasked with carrying out the consensus decision of the community.
There is no "consensus decision". There isn't even an absolute majority, only a relative.
1499
General Discussion / Re: Airdrop 100% profit to bitsharestalk.org (0802 50BTSX)
« on: August 16, 2014, 10:16:53 am »
BTSX ID: pmc
Thanks!
Thanks!
1500
General Discussion / Re: If you need BTSX to finish the registration, Just post your account key here
« on: August 16, 2014, 08:06:47 am »
BTSX6ohcP6jcJeLyN6K794PzWiT9NYVxgPzsU5AkGUW6PXeGAtWyM5
thanks
thanks
