12361
BitShares PTS / Re: Just bought a load of PTS
« on: May 28, 2014, 09:44:14 am »
Lucky you ..
* xeroc is still buying
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.
12362
KeyID / Re: Namecoin airdrop?
« on: May 28, 2014, 09:05:47 am »Hi all, noobie noob here. Figured I'd offer my two cents instead of just lurking.Welcome to the community!
Quote
First of all take this with 84,000 grains of salt, as the so-called Namecoin community is really a collection of unrelated groups. I'm sure that my opinions are at odds with many who also have an interest in Namecoin and other nextgen DNS projects.I can understand your decisions, however, I currently see absolutly no development in namecoin (i am not speaking about price, but about tech development)
An airdrop is not going to be of much interest to me, except for the temporary interest generated by the prospect for making a quick buck. Even if there's some profit to be made, I'm hanging onto my NMC. Like many others, I do not hold a bunch of NMC as an investment in the currency, but rather to use in future. In the longer term I'm swayed by the vision, features, and community.
Kudos again toast and others. I have loads of questions, but I think more reading is required first.
Further, no marketing, no intentions to introduce namecoin to other players, no lobby, just sitting there. That's my feeling, please tell me if I am mistaken.
12363
BitShares PTS / Re: 24 hours passed, stiil not confirmed
« on: May 28, 2014, 09:01:43 am »
Some miners (pool operators) run a flawed software which does not include transactions into blocks.
You have two options:
1.) delete your blockchain files (everything except 'wallet.dat') and reissue your payment
2.) wait until the right pool picks up your transaction and includes it into a block
edit: i'd prefer 2) as rebroadcasting a tx is sometimes a not so good idea
You have two options:
1.) delete your blockchain files (everything except 'wallet.dat') and reissue your payment
2.) wait until the right pool picks up your transaction and includes it into a block
edit: i'd prefer 2) as rebroadcasting a tx is sometimes a not so good idea
12364
General Discussion / Re: New Public XTS Test for Developers and Savvy Users
« on: May 28, 2014, 08:19:29 am »I'll disconnect now.Didn't work out :-( too bad ..
You must try ASAP...
Tell me the result please.I tried
network_add_node "107.170.30.182:5678" onetry
and
network_add_node "107.170.30.182:5678" add
still no connections :-(
anyway .. there seems to be an issue with the seed node max_connection and the p2p-code.
EDIT: thanks anyway
12365
General Discussion / Re: New Public XTS Test for Developers and Savvy Users
« on: May 28, 2014, 07:50:37 am »
I tried
network_add_node "107.170.30.182:5678" onetry
and
network_add_node "107.170.30.182:5678" add
still no connections :-(
network_add_node "107.170.30.182:5678" onetry
and
network_add_node "107.170.30.182:5678" add
still no connections :-(
Quote
{
"blockchain_asset_reg_fee": 301988160,
"blockchain_asset_shares_max": 1000000000000000,
"blockchain_bips_per_share": 12.5,
"blockchain_block_fee_min": 1,
"blockchain_block_interval": 30,
"blockchain_block_num": 0,
"blockchain_block_size_max": 209715,
"blockchain_block_size_target": 104857,
"blockchain_delegate_fire_votes_min": 11428571428571,
"blockchain_delegate_num": 7,
"blockchain_delegate_reg_fee": 43141165,
"blockchain_delegate_reward_min": 200,
"blockchain_id": "09b45e088af94f853ac2ad69b2203e02ee5bbcc23ca353793c48fe23419c06fe",
"blockchain_name_size_max": 63,
"blockchain_name_data_size_max": 4096,
"blockchain_random_seed": "0000000000000000000000000000000000000000",
"blockchain_shares": 80000000000000,
"blockchain_size_max": 107374182400,
"blockchain_symbol": "XTS",
"blockchain_version": 100,
"client_httpd_port": 0,
"client_rpc_port": 0,
"network_num_connections": 0,
"network_num_connections_max": 12,
"network_protocol_version": 100,
"wallet_balance": 0,
"wallet_balance_bips": 0,
"wallet_open": false,
"wallet_unlocked_until": "",
"wallet_version": 100,
"_bitshares_toolkit_revision": "5f61176a67115ea0b0594d218253b0341b063a95",
"_fc_revision": "54c66bbb86770d5d166c8b172b2658e9103e37cb",
"_network_node_id": "cd397fef9148cd08138b32eb803b20249c98f53d"
}
The default node seed is "107.170.30.182:5678"
I am wondering how many is the max connections set in this node?
When the connection is up to the max, If the new node can get other node list from this node?
If the answer is yes, you'll get a list, but I doubt the other nodes can accept your connection request because of the UPNP feature maybe not open.
At least, I can't connect to other node except 107.170.30.182.
I'll try to open UPNP when I arrive home this evening.Code: [Select]alt (locked) >>> get_info
{
...
"network_num_connections": 1,
"network_num_connections_max": 12,
...
}I still cannot connect to network from most recent git-master-headCode: [Select]1693768ms th_a try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/fork_number_db is not upgradeable upgrade_leveldb.cpp:44
1693773ms th_a try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/fork_db is not upgradeable upgrade_leveldb.cpp:44
1693778ms th_a try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/property_db is not upgradeable upgrade_leveldb.cpp:44
1693817ms th_a try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/proposal_db is not upgradeable upgrade_leveldb.cpp:44
1693819ms th_a try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/proposal_vote_db is not upgradeable upgrade_leveldb.cpp:44
1693823ms th_a try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/undo_state_db is not upgradeable upgrade_leveldb.cpp:44
1693826ms th_a try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/block_num_to_id_db is not upgradeable upgrade_leveldb.cpp:44
1693829ms th_a try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/block_id_to_block_db is not upgradeable upgrade_leveldb.cpp:44
1693833ms th_a try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/pending_transaction_db is not upgradeable upgrade_leveldb.cpp:44
1693839ms th_a try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/asset_db is not upgradeable upgrade_leveldb.cpp:44
1693850ms th_a try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/balance_db is not upgradeable upgrade_leveldb.cpp:44
1693857ms th_a try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/name_db is not upgradeable upgrade_leveldb.cpp:44
1693863ms th_a try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/name_index_db is not upgradeable upgrade_leveldb.cpp:44
1693869ms th_a try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/symbol_index_db is not upgradeable upgrade_leveldb.cpp:44
1693874ms th_a try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/delegate_vote_index_db is not upgradeable upgrade_leveldb.cpp:44
1693878ms th_a try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/ask_db is not upgradeable upgrade_leveldb.cpp:44
1693882ms th_a try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/bid_db is not upgradeable upgrade_leveldb.cpp:44
1693886ms th_a try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/short_db is not upgradeable upgrade_leveldb.cpp:44
1693889ms th_a try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/collateral_db is not upgradeable upgrade_leveldb.cpp:44
1693892ms th_a try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/processed_transaction_id_db is not upgradeable upgrade_leveldb.cpp:44
1693908ms th_a load_configuration ] Loaded configuration from file /home/coin/.BitSharesXTS/node_config.json node.cpp:1953
1693914ms th_a try_upgrade_db ] Database /home/coin/.BitSharesXTS/peers.leveldb is not upgradeable upgrade_leveldb.cpp:44
1693914ms th_a trigger_p2p_network_ ] Triggering connect loop now node.cpp:690
1696915ms th_a set_reuse_address ] Error setting SO_REUSEPORT tcp_socket.cpp:226
1696915ms th_a connect_to_p2p_netwo ] listening for connections on endpoint 0.0.0.0:5678 node.cpp:1999
1696915ms th_a connect_to ] node_impl::connect_to(107.170.30.182:5678) node.cpp:2022
1696915ms th_a set_reuse_address ] Error setting SO_REUSEPORT tcp_socket.cpp:167
1696915ms th_a connect_to ] Exception binding outgoing connection to desired local endpoint: bind: Address already in use tcp_socket.cpp:104
1696915ms th_a fetch_sync_items_loo ] beginning another iteration of the sync items loop node.cpp:716
1696915ms th_a fetch_sync_items_loo ] no sync items to fetch right now, going to sleep node.cpp:752
1696915ms th_a p2p_network_connect_ ] Starting an iteration of p2p_network_connect_loop(). node.cpp:602
1696916ms th_a display_current_conn ] Currently have 1 of 8 connections node.cpp:975
1696916ms th_a display_current_conn ] my id is a75359d89e069142f7db0c381de98c19cd24ae89 node.cpp:976
1696916ms th_a display_current_conn ] handshaking: 107.170.30.182:5678 with 0000000000000000000000000000000000000000 [outbound] node.cpp:984
1696916ms th_a p2p_network_connect_ ] Last attempt was 0 seconds ago (disposition: last_connection_failed) node.cpp:641
1696916ms th_a display_current_conn ] Currently have 1 of 8 connections node.cpp:975
1696916ms th_a display_current_conn ] my id is a75359d89e069142f7db0c381de98c19cd24ae89 node.cpp:976
1696916ms th_a display_current_conn ] handshaking: 107.170.30.182:5678 with 0000000000000000000000000000000000000000 [outbound] node.cpp:984
1696916ms th_a p2p_network_connect_ ] Still want to connect to more nodes, but I don't have any good candidates. Trying again in 15 seconds node.cpp:669
1696916ms th_a fetch_items_loop ] beginning an iteration of fetch items (0 items to fetch) node.cpp:773
1696916ms th_a advertise_inventory_ ] beginning an iteration of advertise inventory node.cpp:822
1701922ms upnp operator() ] No valid UPnP IGDs found upnp.cpp:145
1703915ms th_a delegate_loop ] next block time: 19700101T000000 interval: 30 seconds now: 20140528T072823 client.cpp:78
1705915ms th_a delegate_loop ] next block time: 19700101T000000 interval: 30 seconds now: 20140528T072825 client.cpp:78
1707915ms th_a delegate_loop ] next block time: 19700101T000000 interval: 30 seconds now: 20140528T072827 client.cpp:78
1709915ms th_a delegate_loop ] next block time: 19700101T000000 interval: 30 seconds now: 20140528T072829 client.cpp:78
1711916ms th_a delegate_loop ] next block time: 19700101T000000 interval: 30 seconds now: 20140528T072831 client.cpp:78
1711916ms th_a p2p_network_connect_ ] Starting an iteration of p2p_network_connect_loop(). node.cpp:602
1711916ms th_a display_current_conn ] Currently have 1 of 8 connections node.cpp:975
1711916ms th_a display_current_conn ] my id is a75359d89e069142f7db0c381de98c19cd24ae89 node.cpp:976
1711916ms th_a display_current_conn ] handshaking: 107.170.30.182:5678 with 0000000000000000000000000000000000000000 [outbound] node.cpp:984
1711916ms th_a p2p_network_connect_ ] Last attempt was 15 seconds ago (disposition: last_connection_failed) node.cpp:641
1711916ms th_a display_current_conn ] Currently have 1 of 8 connections node.cpp:975
1711916ms th_a display_current_conn ] my id is a75359d89e069142f7db0c381de98c19cd24ae89 node.cpp:976
1711916ms th_a display_current_conn ] handshaking: 107.170.30.182:5678 with 0000000000000000000000000000000000000000 [outbound] node.cpp:984
1711916ms th_a p2p_network_connect_ ] Still want to connect to more nodes, but I don't have any good candidates. Trying again in 15 seconds node.cpp:669
1713916ms th_a delegate_loop ] next block time: 19700101T000000 interval: 30 seconds now: 20140528T072833 client.cpp:78
1715916ms th_a delegate_loop ] next block time: 19700101T000000 interval: 30 seconds now: 20140528T072835 client.cpp:78
1717916ms th_a delegate_loop ] next block time: 19700101T000000 interval: 30 seconds now: 20140528T072837 client.cpp:78
12366
General Discussion / Re: Against PTS2 (naming) and Using the fund in marketing
« on: May 28, 2014, 07:44:38 am »I have to LOL, you are invited?? Who will invite you without Dan? OK, Since you show up and had no intention to commit you are doing a lousy job and keep emphasizing you are doing good, I have to take this little more personal. I apologize in advance.We all like criticism
Quote
1. Look at the community vote https://bitsharestalk.org/index.php?topic=4712.0 and you are still insisting to use those stupid huge human picture. It is so hard to find any useful information now. Good job on the 6th version of the site.Yhea.. that actually sucks as BM himself already made a nice (static-html) webpage which everyone could work on @ github. No idea what the advantages of wordpress are here.
Quote
2. This forum has been the most important marketing portal since beginning and you have only 120 posts here, are you really listening to the community voice? Why BM and toast need to spend so much time here educating people and you are nowhere.That might me unfair. I am no marketing guy but why waste time educating people that are already around in this forum. More important is to educate people that are not! However, I'd really like to see like a 'weekly update' of the mktdirector.
Quote
3. Do you even have a bitcointalk account? Have you post anything there introducing/defending bitshares? What I see is you have to pay others to answer the question in BTT and reddit.BTT is full of shit posts .. Personaly I find it more and more difficult to extract 'usefull(tm)' information from there. Anyway you made a point. I am not sure how much time mktdirector should spend vs. is spending on markting, but BTT probabliy is still a big piece in the picture.
Quote
4. You are paying a third party to run the facebook and twitter account. Have a look how many followers there. And how unprofessional they are answering the questions. Isn't it your key job to have a good social media communication?Google+ also looks bad. :-(
Quote
5. Can you present in any conference if Dan is busy? After being as BIG DIRECTOR for 6 months, I don't think you are capable to do that.I do hope he does not have some real business in hand he kept for secret to get cheap AGS :-( I can remember BM saying sth about a cooperation with maidsafe. Nothing more.
Quote
6. How busy are you to need an assistant???@mkdirector: Have you forgotten about the newsletter, You could at least tell us you opinion about our efforts to create a community version of the newsletter as the last newsletter is several months old!!
Quote
Having about 20k AGS myself, I really want to cry when looking at those smiling pics on bitshares.org. Dare you put up a poll to let community determine your salary? Answer the questions or I will keep asking everyday.Wow .. thats a stake :-) congrats
12367
General Discussion / Re: New Public XTS Test for Developers and Savvy Users
« on: May 28, 2014, 07:29:27 am »
I still cannot connect to network from most recent git-master-head
Code: [Select]
1693768ms th_a try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/fork_number_db is not upgradeable upgrade_leveldb.cpp:44
1693773ms th_a try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/fork_db is not upgradeable upgrade_leveldb.cpp:44
1693778ms th_a try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/property_db is not upgradeable upgrade_leveldb.cpp:44
1693817ms th_a try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/proposal_db is not upgradeable upgrade_leveldb.cpp:44
1693819ms th_a try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/proposal_vote_db is not upgradeable upgrade_leveldb.cpp:44
1693823ms th_a try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/undo_state_db is not upgradeable upgrade_leveldb.cpp:44
1693826ms th_a try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/block_num_to_id_db is not upgradeable upgrade_leveldb.cpp:44
1693829ms th_a try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/block_id_to_block_db is not upgradeable upgrade_leveldb.cpp:44
1693833ms th_a try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/pending_transaction_db is not upgradeable upgrade_leveldb.cpp:44
1693839ms th_a try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/asset_db is not upgradeable upgrade_leveldb.cpp:44
1693850ms th_a try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/balance_db is not upgradeable upgrade_leveldb.cpp:44
1693857ms th_a try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/name_db is not upgradeable upgrade_leveldb.cpp:44
1693863ms th_a try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/name_index_db is not upgradeable upgrade_leveldb.cpp:44
1693869ms th_a try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/symbol_index_db is not upgradeable upgrade_leveldb.cpp:44
1693874ms th_a try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/delegate_vote_index_db is not upgradeable upgrade_leveldb.cpp:44
1693878ms th_a try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/ask_db is not upgradeable upgrade_leveldb.cpp:44
1693882ms th_a try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/bid_db is not upgradeable upgrade_leveldb.cpp:44
1693886ms th_a try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/short_db is not upgradeable upgrade_leveldb.cpp:44
1693889ms th_a try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/collateral_db is not upgradeable upgrade_leveldb.cpp:44
1693892ms th_a try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/processed_transaction_id_db is not upgradeable upgrade_leveldb.cpp:44
1693908ms th_a load_configuration ] Loaded configuration from file /home/coin/.BitSharesXTS/node_config.json node.cpp:1953
1693914ms th_a try_upgrade_db ] Database /home/coin/.BitSharesXTS/peers.leveldb is not upgradeable upgrade_leveldb.cpp:44
1693914ms th_a trigger_p2p_network_ ] Triggering connect loop now node.cpp:690
1696915ms th_a set_reuse_address ] Error setting SO_REUSEPORT tcp_socket.cpp:226
1696915ms th_a connect_to_p2p_netwo ] listening for connections on endpoint 0.0.0.0:5678 node.cpp:1999
1696915ms th_a connect_to ] node_impl::connect_to(107.170.30.182:5678) node.cpp:2022
1696915ms th_a set_reuse_address ] Error setting SO_REUSEPORT tcp_socket.cpp:167
1696915ms th_a connect_to ] Exception binding outgoing connection to desired local endpoint: bind: Address already in use tcp_socket.cpp:104
1696915ms th_a fetch_sync_items_loo ] beginning another iteration of the sync items loop node.cpp:716
1696915ms th_a fetch_sync_items_loo ] no sync items to fetch right now, going to sleep node.cpp:752
1696915ms th_a p2p_network_connect_ ] Starting an iteration of p2p_network_connect_loop(). node.cpp:602
1696916ms th_a display_current_conn ] Currently have 1 of 8 connections node.cpp:975
1696916ms th_a display_current_conn ] my id is a75359d89e069142f7db0c381de98c19cd24ae89 node.cpp:976
1696916ms th_a display_current_conn ] handshaking: 107.170.30.182:5678 with 0000000000000000000000000000000000000000 [outbound] node.cpp:984
1696916ms th_a p2p_network_connect_ ] Last attempt was 0 seconds ago (disposition: last_connection_failed) node.cpp:641
1696916ms th_a display_current_conn ] Currently have 1 of 8 connections node.cpp:975
1696916ms th_a display_current_conn ] my id is a75359d89e069142f7db0c381de98c19cd24ae89 node.cpp:976
1696916ms th_a display_current_conn ] handshaking: 107.170.30.182:5678 with 0000000000000000000000000000000000000000 [outbound] node.cpp:984
1696916ms th_a p2p_network_connect_ ] Still want to connect to more nodes, but I don't have any good candidates. Trying again in 15 seconds node.cpp:669
1696916ms th_a fetch_items_loop ] beginning an iteration of fetch items (0 items to fetch) node.cpp:773
1696916ms th_a advertise_inventory_ ] beginning an iteration of advertise inventory node.cpp:822
1701922ms upnp operator() ] No valid UPnP IGDs found upnp.cpp:145
1703915ms th_a delegate_loop ] next block time: 19700101T000000 interval: 30 seconds now: 20140528T072823 client.cpp:78
1705915ms th_a delegate_loop ] next block time: 19700101T000000 interval: 30 seconds now: 20140528T072825 client.cpp:78
1707915ms th_a delegate_loop ] next block time: 19700101T000000 interval: 30 seconds now: 20140528T072827 client.cpp:78
1709915ms th_a delegate_loop ] next block time: 19700101T000000 interval: 30 seconds now: 20140528T072829 client.cpp:78
1711916ms th_a delegate_loop ] next block time: 19700101T000000 interval: 30 seconds now: 20140528T072831 client.cpp:78
1711916ms th_a p2p_network_connect_ ] Starting an iteration of p2p_network_connect_loop(). node.cpp:602
1711916ms th_a display_current_conn ] Currently have 1 of 8 connections node.cpp:975
1711916ms th_a display_current_conn ] my id is a75359d89e069142f7db0c381de98c19cd24ae89 node.cpp:976
1711916ms th_a display_current_conn ] handshaking: 107.170.30.182:5678 with 0000000000000000000000000000000000000000 [outbound] node.cpp:984
1711916ms th_a p2p_network_connect_ ] Last attempt was 15 seconds ago (disposition: last_connection_failed) node.cpp:641
1711916ms th_a display_current_conn ] Currently have 1 of 8 connections node.cpp:975
1711916ms th_a display_current_conn ] my id is a75359d89e069142f7db0c381de98c19cd24ae89 node.cpp:976
1711916ms th_a display_current_conn ] handshaking: 107.170.30.182:5678 with 0000000000000000000000000000000000000000 [outbound] node.cpp:984
1711916ms th_a p2p_network_connect_ ] Still want to connect to more nodes, but I don't have any good candidates. Trying again in 15 seconds node.cpp:669
1713916ms th_a delegate_loop ] next block time: 19700101T000000 interval: 30 seconds now: 20140528T072833 client.cpp:78
1715916ms th_a delegate_loop ] next block time: 19700101T000000 interval: 30 seconds now: 20140528T072835 client.cpp:78
1717916ms th_a delegate_loop ] next block time: 19700101T000000 interval: 30 seconds now: 20140528T072837 client.cpp:78
12368
General Discussion / Re: MirrorChain--to solve the security threat during the new DACs distribution
« on: May 28, 2014, 07:27:55 am »I dont understand much of the ECC magic but couldn't we go for a hybrid, such that if the pubkeys is known we can do ECC magic .. if not the owner needs to work on the actual privkey ..Maybe we can use some ellyptic curve magic to solve the issue ... much like what TITAN does?The problem is that without the actual public key of the account holder you cannot do any operation other than signature verification and that requires the private key.
If we had the public key for every address in the snapshot then it would be possible to separate out the tool that imports the private keys for each chain from the chain itself.
I think the way we can get around this is to have a separate 'trusted' process that can sign arbitrary data for a new chain. This process would report to the new DAC all of the addresses it can sign for.
This way the new DAC never sees your private key, but can still use it for signing transactions *FOR THAT DAC ONLY*.
we could then update the pubkeys for new DACS on a regular bases using most recent blockchain (assuming no one really can break ripmed150(sha256(pubkey)))
Just asking
;-)
12371
BitShares PTS / Re: BitShares-PTS 1.0 Release (2.18.2014)
« on: May 27, 2014, 03:20:17 pm »
Network is ultra slow atm ... upgrade to new system soon ..
12372
BitShares PTS / Re: 111* days estimated for Difficulty to retarget. Could this kill PTS?
« on: May 27, 2014, 02:08:02 pm »Plenty of time left .. pretty sure that retarget will not happen :-)how long until next retarget?
You can check here:
http://mrx.im/pts.php
Time to retarget: 139d 09:44:40 (2014-10-14 08:23:49 UTC+9)
12373
General Discussion / Re: Airdrop concerns with Lottoshares
« on: May 27, 2014, 02:07:13 pm »OK, so now you have hit on something really, really BIG! This is where PTS/AGS earn their 10%s.Probably
This community is the single biggest group of well-informed experts on what makes a good BitShares DAC.lol .. i am just amused about .... rectal examination .... too funny
When a developer honors this community, it is, in part, to take advantage of that expertise to get a thorough rectal examination and vetting that they can point to with pride.
(Presumably, if this community finds no show-stoppers and is excited about the product, that is the primordial DAC equivalent of an endorsement from Underwriter's Labs, Consumer Reports and an alphabet soup of consumer protection agencies BEUC/SPCA/PETA/EPA, etc.)Thats actually what I also mentioned on an other thread, that this might be a very good opportunity to earn money here.
This is not something I3 can do, but it is something the BitShares Community can do!
However, my abilities in reading code are somewhat limited :-(
//edit: link: https://bitsharestalk.org/index.php?topic=4737.msg60801#msg60801
12374
General Discussion / Re: Airdrop concerns with Lottoshares
« on: May 27, 2014, 02:05:04 pm »Check source code (in order to prevent stealing of privkeys) probably mean that we also should publish precompiled binaries?That's probably the consequence ... too good we already have jenkins in place :-) *thumbs up*
Update: As idea, we can distribute binaries over BitShares nightly build system.
12375
BitShares PTS / Re: 111* days estimated for Difficulty to retarget. Could this kill PTS?
« on: May 27, 2014, 01:36:53 pm »
how long until next retarget?
is it even worth talking about it? or will PTS2 (or whatever it will be called, i.e. TitanTokens :-) ) be available earlier (i.e. snapshot)?
is it even worth talking about it? or will PTS2 (or whatever it will be called, i.e. TitanTokens :-) ) be available earlier (i.e. snapshot)?
