Isn't it 1000 keys for bitcoin and 10,000 for Dash ?
(the number of keys was increased so that mixing should not use up all the keys in backup)
I think there is still 100 keys for btc and 1001 for dash on default. Though you can increase it at any time Yer, you are right, I just checked it  This is correct if you're looking at the wallet but I took the question as the TOTAL keys that can be made I don't think there is a maximum for bitcoin or Dash, it's just a matter of how many are kept pre-generated  There is a maximum, its 2^256 private keys for the max of 2^160 addresses and 2^96 keys for each address! http://bitcoin.stackexchange.com/questions/25069/can-two-private-keys-generate-the-same-public-bitcoin-addressThere are 2^160 possible addresses, and 2^256 possible private keys, so each address corresponds to roughly 2^(256-160)=2^96 private keys. Any of these will generate the same address and thus be able to spend the money owned by that address. Since 2^160 is so large, however, it would take a near-eternity to find any collisions. |
|
|
|
Isn't it 1000 keys for bitcoin and 10,000 for Dash ?
(the number of keys was increased so that mixing should not use up all the keys in backup)
I think there is still 100 keys for btc and 1001 for dash on default. Though you can increase it at any time Yer, you are right, I just checked it |
|
|
|
How many are possible dash addresses that can be generated ? How many GB space need for all of them ? the numbers are same as BTC or high or lower ?
Unlimited number of address - as each would have their own private key Isn't it 1000 keys for bitcoin and 10,000 for Dash ? (the number of keys was increased so that mixing should not use up all the keys in backup) The Dash total blockchain uses about 1 gigabyte and bitcoin uses 36 gigabytes, the number of keys has very difference on the size. |
|
|
|
Did we lose some MN's?
For me Dashninja is showing: Total Masternodes: 2939 = 2902 actives + 37 inactives [2682 unique IPs] (Last refresh: Mon Aug 03 2015 3:15:53 PM) It looks pretty normal to me, I do remember there is a new investor potentially buying 100 K DASH OTC, so those nodes may go down and back up at some point if the deal happens. Not sure which is more correct atm: http://178.254.18.153/~pub/masternode_count.png @ 2,919 or https://dash-stats.firebaseapp.com @ 2,896 ? Mine are still all up, but yes there well could be approx 100 MN changing hands OTC early this week which will show up in the total live as they are taken down and set up elsewhere, better distribution of coins and voting, also it was the buyer who approached me for this deal, four others are also showing interest with amounts from 600 DASH to a few MN worth and a possible for 25 MN, once these have completed then I will be much more reluctant to part with any I imagine. Good luck with the redistribution,more strong hands and new countries, the better Btw, I usually get the masternode number from the local wallet using 'masternode count' in debug console after waiting a few minutes for it to stop incrementing after collecting the information, atm masternodes = 2893 |
|
|
|
Tao sync ratio update  I have measured bitcoin (v.0.11.0) first, before the much anticipated version V12 of Dash, this will be updated on release, the conclusion so far is that the Tao sync ratio for bitcoin(v.0.11.0) is 11.2% faster than bitcoin (v.0.10.0) https://dashtalk.org/threads/dash-versus-bitcoin-versus-darkcoin-wallet-update-benchmark-times.4479/
''Bitcoin (v0.11.0) = Tao ratio = 4.144 seconds / hour + (9.3 seconds indexing startup time, needed 3 runs for best time)''Have you noticed that bitcoin's peers are outdated, this must be slower for seeding I imagine .. |
|
|
|
For GOD's SAKE! WTF! ANY redheads are GOLDEN here! Throw out the blonds, the brunets the greys, but DO NOT throw out any REDHEADS or this project is totally sunk! What's wrong with you people?
ahahaha!!! Red's are indeed an endangered species! Really! Like... scientifically! Tante, here's one for you! https://www.youtube.com/watch?v=p7UGjNKKXH8LOL, I simply can't understand why people don't like freckles and red hair...  |
|
|
|
Hasta la vista, reference node  Hasta La Vista, reference node! |
|
|
|
Please stop promoting Moner__ & Byteco__ shit in this DASH topic!
I understand that their adepts are so desperate they can't find an attention anywhere else... But why Dashers are helping them to post and promote here?
If you really want to discuss their shit - just report their ignorant posts to moderator - than go to their thread and discuss all this there...
Please keep this topic clean from their ignorant advertising!
Agreed, am not interested in discussing how Monero functions, we don't go into their thread and start fanatically going on and on about their coin ad nauseum , I have most of them on ignore because they are troll-like, boring, infantile and predictable in their comments. (and this comment will result in even more misinformed agenda ridden spam, trolololol) ~~Peace to all~~ |
|
|
|
Here's an interesting thought experiment... The only real problem with that logic is we need to store the transactions in a block after they happen and blocks have an upper limit on size. 3000 tx per second that would mean we have 450000.0 transactions in a block. I'm getting about 107MB per block with some rough math. If the network requires about 4x the blocksize in bandwidth, we could possibly need about 100MB a minute. To get 100MB a minute consistently we could have a 3rd tier that lives on a high performance network (maybe a specific zone of AWS for high performance computing). If you want to use our high performance network, you would switch through a 2-way peg to this second chain, which has pretty much infinite speed. We could actually have a bunch of these, all on separate networks throughout the world, so that if one is having problems, there's always redundancy. Hmm...  The masternode network + quorums is quite powerful for solving these types of problems. Question; Would that be 100 mb a minute be the same size on the blockchain? How would we store such a behemoth? I mean seriously, no matter how you shake it, blockchain size is going to have to be dealt with some day, and somewhere, I think most would agree, the whole thing must be stored in it's entirety, decentralized. This will be a problem for everyone. What do you think needs to be done? I can see chopping it up and storing sections of it, redundantly, amongst groups of nodes, perhaps in a compressed format, digitally signed and archived (again redundantly) with the "working" chain being a trimmed version. What other options might there be? Thanks for your opinion! That's the on-chain size, but by then we'll have pruning. So we'll just be storing unspent outputs. Even if the blockchain is a terabyte pruned, it's only being stored by the masternodes on this separate chain. We're talking about having billions of transactions per day, that means that Dash is worth tons of money. This network would be ran by the masternode operators and they would still be earning a share of the revenue for providing the services. At this point, the services are very costly, but the rewards will be even greater. This is going to be a business for the masternode operators, something like what's happening with Bitcoin pools but much more decentralized. So a full blockchain for the masternoders and a 'pruned' one for general full client use, is it known how much space can be saved by this technique of streamlining the blockchain ? |
|
|
|
Splendid. Three+ orders of magnitude better tx throughput than Bitcoin then. I just sent 2000 IX and they all validated upto about 300 within minutes and only reason it stopped was there were so many change addresses created that it refused to send any more IX because of zero confirmations, haven't worked a way round that one yet , don't know about stressing IX but it certainly stressed the computer, I heard the fan speed up, lol |
|
|
|
Bitcoin currently handles 7 unconfirmed tx per second + confirmation/waiting time
DASH handles 10 confirmed tx per second and you can walk out the shop with the merchant safe and happy.
Not quite right, the entire Bitcoin network handles a maximum of 7 txes per second. Each IX only requires a tiny subset of the 3000 MN total to work. You're looking at tx throughput two orders of magnitude+ better than BTC, each one in seconds, not minutes/hours. So if the subset is 10 for example, at 3k M-Nodes the TPS would be 3,000 as well, I assume? That's 1k more than VISA handles atm. This is a very interesting read on that matter: https://en.bitcoin.it/wiki/ScalabilityIf 10 MNs are needed for each IX then with 3000 MNs you'd have theoretical capacity for 300 simultaneous IX's. There are going to be overheads, and some MNs may be tied up doing DS or something else, but you get the idea. I don't know if or how the concept of MN multithreading/multitasking applies, but there's probably room to squeeze a shitload more efficiency out of the system yet. 300 is not the maximum, Evan said its down to the amount of memory of the masternodes, the upper limit is unknown. We were sending hundreds of IX in testnet with only 150 masternodes and they all worked up until someone reduced the number of nodes, there looked to be a failure point were they return to proof of work but its pretty low node count wise and when scaled up to 3000 nodes may be impossible to break due to the strength of the network. |
|
|
|
Looks infinitely scalable to me, might have to test 1 million instantX transactions just for the sheer hell of it ' So how many tx a quorum(10 MNs) can take? Is it a matter of bandwidth or...please axplain??
If 30000 or more itx hit MN network, what then? Can a MN on average be a part of 3000 quorums or more?' --Lukas_Jackson-- ' Sure, the only limit to the system is the amount of memory we have available. But then again, we have a 2-tier network... so we can just require beefy masternodes. ' --Evan Duffield-- |
|
|
|
Why does the network have so much new capacity with this release ?
Do you mean testnet? Evan reckons it will be slower on mainnet but even so ... |
|
|
|
Great I'm wondering...Is that a max you tried to squeeze out in this test? Did you try 0.01s or lower? I just got 100 instantly successful instantX's out of 100, this new command is excellent, it pumps in more transactions than you could ever click, what a stress test, shows what instantX is really capable of, can't wait to see this on mainnet |
|
|
|
This just beautifully illustrates toknormal's point on how programmers aren't economists. In German there's a term for people who attempt to be experts beyond their own actual area of expertise and rightfully fail at such. It's "Fachidiot" and literally translates to "subject idiot", meaning you're so focussed on your own subject that you fail to apply it in a meaningful way beyond that scope unable to crossover to other fields. Maxwell sure is a Fachidiot. That's really funny, I didn't know that one. What's interesting with Evan is that he is not just a programmer (since age 15), but also a Financial analyzer, having created his own analysis of the stock market and selling his data through his website when he was still a kid. But, although he always seems to be way ahead of everyone, he also asks for opinions, yet has a philosophy that he is following to solidify the foundation of Dash. So he gathers everyone, listens to all opinions, and finds the right direction to go in. I've been excited since day one, impressed since at least day 14, at least! Look at the block attributes chart, almost hitting the 1 meg ceiling and averaging around 800 kbytes, not much headroom left at all, https://statoshi.info/dashboard/db/blocks |
|
|
|
Interesting debate going on about blocksize, scaling problems and what Satoshi thought about it, http://www.reddit.com/r/Bitcoin/comments/3f26b7/thank_you_mike_hearn_for_sticking_up_for_us_this/https://bitcointalk.org/index.php?topic=1790.msg28917#msg28917'Piling every proof-of-work quorum system in the world into one dataset doesn't scale.
Bitcoin and BitDNS can be used separately. Users shouldn't have to download all of both to use one or the other. BitDNS users may not want to download everything the next several unrelated networks decide to pile in either.
The networks need to have separate fates. BitDNS users might be completely liberal about adding any large data features since relatively few domain registrars are needed, while Bitcoin users might get increasingly tyrannical about limiting the size of the chain so it's easy for lots of users and small devices.'~~Satoshi~~ |
|
|
|
Super! what fun  So you are 1st september - 7th september at midnight. I will bet 8th september to 15th september for 1 Dash My payment address, XuxAsDdAYwRd6dY9BJrJHWMaje9ThgwveC P.s. please no sneaky adding your masternodes at last minute at the start of september to manipulate the bet Ok, perfect. Don't worry I don't have enough MN to play this kind of sneaky, and prefer lose 1 DASH on my bet that some payments of my MNs And my next MN I'll put it online tonight Bet on, I did think of overlapping my week so we could potentially have a draw but didn't want to complicate it, if anyone else joins we can have a mexican standoff of 3 competing weeks with a larger prize |
|
|
|
wrong stat because of absent cheap vps service in my state, I use USA server. I'd added a MN in my country to insert in the MN list. Very few in the Southern Hemisphere, but same could be said of bitcoin seed nodes. |
|
|
|
Does anyone want to bet 1 dash with me on what week we will reach 3000 masternodes for fun?
I will let you choose a particular (7 day) week first then I will choose another week slot.
(suggest that the weeks can overlap but if result is on the same day as both choose then no payouts are made)
look competition in setting a MN. It is very interesting watching the MN number changing. I think under 20 days to reach 3000 MNs. It looked like end of July a month ago but the gradient is decreasing, I would say early September if the trend continues. @Sub-Ether: I already put a date one week ago and I'm ok to bet with you for this date (1 September 2015). Just our of interest in the build up to 3k MN's, going back in time and trying to find any predictions made by the community or Evan on when 3000 MN would be reached. I'll see what I can find. In the meantime, anyone care to guess when we'll reach 3k, days or weeks I bite : 1 september 2015 we'll reach 3000.I think it's normal that increasing of number of MN, maybe because last month period I almost win the double than the teorical reward for MN. EDIT: after some more calculation, last month I win 50% more with my MNs than 2 month ago. (In DASH) (I took into account in the date that I'll install a new MN in ~10 days ) Super! what fun So you are 1st september - 7th september at midnight. I will bet 8th september to 15th september for 1 Dash My payment address, XuxAsDdAYwRd6dY9BJrJHWMaje9ThgwveC P.s. please no sneaky adding your masternodes at last minute at the start of september to manipulate the bet |
|
|
|
|
Show Posts
