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 - Spectral

Pages: 1 2 3 [4] 5
46
General Discussion / Re: October 5 Test Network
« on: October 06, 2015, 12:19:58 am »
**************************************************************************************************
EDIT: PLEASE Disregard this whole post, I think I was on a private chain pretty much on my own.
**************************************************************************************************

Witness 'spectral' is up. I think.

EDIT: The witness is running on 2 Cores, 4GB RAM, 100GB SSD

Code: [Select]
get_witness spectral
{
  "id": "1.6.12",
  "witness_account": "1.2.73210",
  "last_aslot": 0,
  "signing_key": "GPH8ZWNd9K82gPqKVDbkK8etaYTBMQ3ME3MTQ6HqF586ZbMLrZ5DH",
  "vote_id": "1:22",
  "total_votes": 0,
  "url": "bitspace.no",
  "total_missed": 0,
  "last_confirmed_block_num": 0
}

BUT I'm somewhat confused right now. After creating the witness and getting the witness ID, I closed down the cli_wallet, and fixed the witness config file. Good.

When I started up the witness again, it complained that there were no blocks received. So I closed it and tried to restart it with --resync-blockchain. That didn't fix it, but I waited abit and it fixed itself. Problem solved, I thought.

So now I try to fire up the cli_wallet again: I can't see any balances in my account. When I try "get_witness spectral" I get this output:

Code: [Select]
get_witness spectral
0 exception: unspecified
No account or witness named spectral
    {"account":"spectral"}
    th_a  wallet.cpp:1310 get_witness

    {"owner_account":"spectral"}
    th_a  wallet.cpp:1314 get_witness

I'm not sure if it will fix itself, or has something gone terribly wrong and i should remake the wallet?


btw, witness output is looking like this:
Code: [Select]
1419531ms th_a       application.cpp:432           handle_transaction   ] Got transaction from network
1419684ms th_a       application.cpp:432           handle_transaction   ] Got transaction from network
1419799ms th_a       application.cpp:388           handle_block         ] Got block #12018 with time 2015-10-06T00:23:39 from network with latency of 800 ms from init1
1419904ms th_a       application.cpp:518           get_item             ] Serving up block #12018
1420505ms th_a       application.cpp:518           get_item             ] Serving up block #12018
1421324ms th_a       application.cpp:518           get_item             ] Serving up block #12018
1422000ms th_a       witness.cpp:182               block_production_loo ] Not producing block because it isn't my turn
1422276ms th_a       application.cpp:388           handle_block         ] Got block #12019 with time 2015-10-06T00:23:42 from network with latency of 278 ms from roadscape
1422370ms th_a       application.cpp:518           get_item             ] Serving up block #12019
1425000ms th_a       witness.cpp:182               block_production_loo ] Not producing block because it isn't my turn
1425201ms th_a       application.cpp:388           handle_block         ] Got block #12020 with time 2015-10-06T00:23:45 from network with latency of 202 ms from init5
1428000ms th_a       witness.cpp:182               block_production_loo ] Not producing block because it isn't my turn
1428056ms th_a       application.cpp:388           handle_block         ] Got block #12021 with time 2015-10-06T00:23:48 from network with latency of 57 ms from bhuz
1428150ms th_a       application.cpp:518           get_item             ] Serving up block #12021
1431000ms th_a       witness.cpp:182               block_production_loo ] Not producing block because it isn't my turn
1431202ms th_a       application.cpp:388           handle_block         ] Got block #12022 with time 2015-10-06T00:23:51 from network with latency of 203 ms from init3
1434000ms th_a       witness.cpp:182               block_production_loo ] Not producing block because it isn't my turn
1434203ms th_a       application.cpp:388           handle_block         ] Got block #12023 with time 2015-10-06T00:23:54 from network with latency of 205 ms from init9
1437000ms th_a       witness.cpp:182               block_production_loo ] Not producing block because it isn't my turn
1437203ms th_a       application.cpp:388           handle_block         ] Got block #12024 with time 2015-10-06T00:23:57 from network with latency of 204 ms from init4

**************************************************************************************************
EDIT: PLEASE Disregard this whole post, I think I was on a private chain pretty much on my own.
**************************************************************************************************

47
General Discussion / Re: October 5 Test Network
« on: October 05, 2015, 11:34:17 pm »
need 5000 core for my account to be wittiness :  bue
Done.  [EDIT: I suppose not, I think I was on my own private chain]

If someone needs some CORE, I have abit more this time around, please ask.

My witness will be up any minute...

48
General Discussion / Re: October 2nd Test Network
« on: October 04, 2015, 08:51:21 pm »
You may be right clayop, but do we need to concern ourselves with that right now? IMO it's more important to address the functionality and feature set that will be available at launch.

Out of the gate we probably won't require 1000 TPS. I do recognize that is only 10% of our claims, and if we DID have a massive response on the launch and we couldn't handle it, it would be very bad indeed.

I'm not sure where the best balance is and what our testing goals should be, but I think we need to get serious very quickly and figure that out, devise a plan to reach those goals and coordinate our efforts to achieve them.

Exactly.. and if each tx costs $0.01, 100 TPS "attacks" cost $1/second, or $3,600/hr. :)

Well, that's not really expensive... 3600 USD will give you:

1 hour of 100TPS attack or... 30 seconds of 12000 TPS attack. Is that not enough to bring down the network?

49
General Discussion / Re: October 2nd Test Network
« on: October 04, 2015, 08:31:01 pm »
I'm not sure where the best balance is and what our testing goals should be, but I think we need to get serious very quickly and figure that out, devise a plan to reach those goals and coordinate our efforts to achieve them.

+5%

That sounds about right. A launch target TPS could be specified, the minimum requirement to meet that target would be identified, so the recommended witness minimum specification would be ready at launch.

Maybe there should even be a max TPS cap (possibly a votable parameter), to protect the network from overload. Is spam an attack vector into BitShares?

50
General Discussion / Re: October 2nd Test Network
« on: October 04, 2015, 03:19:14 pm »
I have a registered witness, but I'm not yet voted in: 'bitspace-testaccount1'. Is there anything I can do to help?

I can check back here every half hour or so today.

51
General Discussion / Re: October 2nd Test Network
« on: October 04, 2015, 10:59:38 am »
My witness (which was not voted in) currently has the following output, and just keeps going like that... 'bitspace-testaccount1'

Code: [Select]
3221000ms th_a       witness.cpp:182               block_production_loo ] Not producing block because it isn't my turn
3222000ms th_a       witness.cpp:182               block_production_loo ] Not producing block because it isn't my turn
3223000ms th_a       witness.cpp:182               block_production_loo ] Not producing block because it isn't my turn
3224000ms th_a       witness.cpp:182               block_production_loo ] Not producing block because it isn't my turn

The CLI interface is still working.

52
General Discussion / Re: October 2nd Test Network
« on: October 04, 2015, 12:04:13 am »
thanks to spartako(again!) and jtm1 for the CORE!

Witness is up and running now, please vote! :)

Code: [Select]
get_witness bitspace-testaccount1
{
  "id": "1.6.35",
  "witness_account": "1.2.8876",
  "last_aslot": 0,
  "signing_key": "GPH8B2qHWXkRiJpthDcq1TGv3MQEMzuRz6wXRnk2rFyLWLUL4ZYtA",
  "vote_id": "1:56",
  "total_votes": 1002444239,
  "url": "bitspace.no",
  "total_missed": 0
}

Can anyone tell me how I can see voting information/percentages/standings? I see that I have 1002444239 votes already, but what does that number mean?


@Thom, it's not much, but...
Code: [Select]
transfer bitspace-testaccount1 delegate.verbaltech 5000 CORE "passing on the love" true
{
  "ref_block_num": 36472,
  "ref_block_prefix": 2363118095,



Edit: w00t 4K txs in one block!
http://imgur.com/gallery/4BAxf4n

53
General Discussion / Re: October 2nd Test Network
« on: October 03, 2015, 06:53:03 pm »
spartako, thank you again for sending CORE! I managed to upgrade my account now :)

Unfortunately, I'm still short 5000 CORE to actually create a witness. Could someone please send another 5000 to account:
'bitspace-testaccount1'?

In case anyone wonders, the total CORE amount needed to register a witness is 15000 CORE. 10k for the account upgrade + 5K for creating the witness (unless I'm missing something)

54
General Discussion / Re: October 2nd Test Network
« on: October 02, 2015, 11:33:51 pm »
Do I need to import a certain type of account to become a lifetime member, like a delegate account or a short name account? I am wary of dumping owner keys in clear text of a delegate account or an account with larger funds... should I be doing that?

I'm stuck with 5000 CORE, and can't upgrade. Account: bitspace-testaccount1

55
General Discussion / Re: October 2nd Test Network
« on: October 02, 2015, 10:29:05 pm »
spartako, thank you for the CORE :)

I imported account 'bitspace-testaccount1', I think it is working properly, and it is funded.

How much CORE is actually needed to get a witness up and running? It would seem I need 10k to become lifetime member first. After that?

Code: [Select]
itr->get_balance() >= -delta: Insufficient Balance: bitspace-testaccount1's balance of 5044.50000 CORE is less than required 10000 CORE
    {"a":"bitspace-testaccount1","b":"5044.50000 CORE","r":"10000 CORE"}


Also I feel I need to make a comment to everyone contributing since the early times: Great work on treading the ground and on the documentation! The whole procedure is much easier to follow now than it was in the beginning. +5% +5% +5%

56
General Discussion / Re: October 2nd Test Network
« on: October 02, 2015, 02:48:32 pm »
Hello good people,

Sorry to join the testing so late, I've been spending the last few days catching up on the progress so far.

I will do my best to get a witness up and running this evening.

spartako, can I please haz some CORE to 'bitspace-testaccount1' for the occasion?


Spectral

57
General Discussion / Re: Initial Witness Pay & Number of Witnesses
« on: September 22, 2015, 08:10:15 pm »

BitShares may be be doing things more efficiently than Bitcoin, but I'm struggling to see how a big actor will have any problem whatsoever taking down 17 witnesses running on 300$ a month. Now I'm not a hacker or security expert, but I've seen how something so small as the newly set up Norwegian Pirate Party DNS server (combatting Pirate Bay censorship) may quickly find itself under heavy DDOS fire. Why would something like this not pose a danger to the BitShares network, with our portfolio of powerful enemies?

A delegate can move their block signing node to any computer under their control connected to the internet in a matter of seconds. This makes a DDOS attack nearly impossible.

In detail:
1) You notice your node is missing blocks and can't log in to your server due to DDOS
2) Connect to another computer you control, update_witness with new signing key

This allows your new witness to sign blocks and prevents your old witness, in the event the DDOS is not a complete shutout or ends, from double signing.

I guess this can be done in theory, but will it work in practice?
1. Will witnesses respond quickly enough (within seconds or minutes)?
2. Will the alert witnesses have servers on standby, compiled and ready with fully loaded blockchains?
3. Can 17 witnesses defend against a dedicated attacker keeping it up for, say, 48 hours?

If there are all those spare witnesses on standby we're not really talking about 17 witnesses cost-wise anyway. They might as well be signing blocks.

I'm seeing a complete blackout of the BitShares network within minutes, and a serious struggle to get it back up again.

58
General Discussion / Re: Initial Witness Pay & Number of Witnesses
« on: September 22, 2015, 06:30:01 pm »
actually bitcoin is controlled by top 5 mine pool ,   do you remember  5 mine pool in china refuse update the max block size
and most of miner don`t take care of chain

That is a decision-making issue, not a security issue. As soon as it turns into a security issue, miners leave. Remember that miners have a huge economic incentive to keep Bitcoin safe and prosperous, just like whales in BitShares have a huge economic incentive to keep BitShares safe and prosperous.

Even so, decisions are made very slowly in Bitcoin. The agile DPOS decision-making mechanism is one of BitShares' main selling points.

59
General Discussion / Re: Initial Witness Pay & Number of Witnesses
« on: September 22, 2015, 05:04:03 pm »
The bitcoin network spends 25 BTC every 10 minutes on security, that's $33k per day. How much does it cost to elect 17 witnesses? ...Once one person does that, it's goodbye chain.

This.  +5%

There is no doubt that Bitcoin has its weaknesses in both decentralization and security (those are not always the same). But anyone claiming that BitShares, as it stands today, has security anywhere near that of Bitcoin is in need of a serious reality check. If you want to attack the Bitcoin network directly (disable it), you need to attack ~6000 full nodes and disable a good chunk of the mining power so that block processing is effectively disabled. With pool-miners essentially able to switch pools at a whim, this must be an extremely difficult operation. If it was feasible (with Bitcoin's 3-4 billion USD market cap) it would have been done already. Let's not arrogantly dismiss Bitcoin's proven security.

As far as I can tell, one of the real dangers to Bitcoin right now is someone controlling a majority of the core devs and driving opinion that way (opinion influences nodes and miners). The recent block size debate has taught us that is still a weakness of Bitcoin. Taking control of mining power is extremely expensive, and can today only be done by huge actors that are good at staying hidden for an extended period of time.

BitShares may be be doing things more efficiently than Bitcoin, but I'm struggling to see how a big actor will have any problem whatsoever taking down 17 witnesses running on 300$ a month. Now I'm not a hacker or security expert, but I've seen how something so small as the newly set up Norwegian Pirate Party DNS server (combatting Pirate Bay censorship) may quickly find itself under heavy DDOS fire. Why would something like this not pose a danger to the BitShares network, with our portfolio of powerful enemies?

I'm thinking that if there is a possible attack vector into BitShares, it will be used. Distributing witness control over several 100 will make it more robust. We need to be proactive with BitShares security, better too much than too little. If the BitShares network is only once attacked and driven to a halt, the crypto community will nod their heads and go "Mhm, that's what we thought. Game over."

60
General Discussion / Re: Initial Witness Pay & Number of Witnesses
« on: September 22, 2015, 02:44:48 pm »
I'm somewhat puzzled by this discussion...

How important is securing the network which is the witness role? How big of a hit would BitShares take if security was compromised? Isn't it better to aim too high than too low?

Bribery, persecution of individuals, DDOS attacks? Do you guys really believe that 17 witnesses is enough decentralization for fighting big government? You may laugh at the Bitcoin crowd, but they know what it means to be under attack. BitShares is still too small to have felt the spotlight, and we're the ones going for the throat of the banks.

Is a potential 100 million dollar financial network really going to run on 17 VPSes costing $40 each? Are we really going to limit the cost of the security for this network to $8160 a year? That sounds kind of absurd to me.

Bitcoin is currently spending more than 200 million dollars on security. Considering the market cap, that is of course not a fair comparison, but even if BitShares brought that number down to 100K (~0.67% of current market cap) it would still be an incredible improvement over Bitcoin.

When I envision the BitShares 2.0 network 2 years into the future, I see 300 high-power witnesses running the network from all corners of the world. The difficulty and cost of attacking the BitShares Network is absolutely mind-boggling, as it should be.

Also, denominating witness pay in BTS is more useful than USD. A higher BTS price means more adoption, higher volume, which in turn places higher requirements on the witnesses. Also, witnesses will participate who actually believe in BTS, not just to make a quick buck.

To sum it up, 17 is way too low. It is natural that the number of witnesses will increase as we grow, not decrease. Start out at 67 witnesses with the option of increasing the number with no upper limit. Keep in mind, letting people run a witness also educates people about BitShares (like me). If you later want to increase from 17 to 35, how long will it take to get 18 qualified admins to jump in?

My 2 BTS. Help me understand why I'm wrong.

Pages: 1 2 3 [4] 5