Btw, I am trying to import one of them free priv keys  Dude I'm importing them all. lol My wallet can hardly handle it. Well actually it can't. Got some btc buts its conflicting when I send it and disappearing from the wallet all the time, figured I would be too late  This dude keeps robbing me blind  1Efci3dbnS9E77BEhyY4LMkjrvCx5LDDMW I got some too, but I dont hold high hopes to be in time to claim by sending it off. There are more private keys released if you want to keep trying. This is the stress test. They are just having anyone that wants to claim the bitcoin do the test for them. Plus now there are multiple users trying to get the same transactions. Smart in a way. So we had a backlog of 60MB(10hrs) of transactions last night. Now we are at 160MB(26.6hrs). It looks like the back log increases an hour every hour. Anyone actually wanting to send bitcoin should raise the fee to at least .00004, this will need to be higher as the test goes on. For anyone interested, each private key is filled with .00001 transactions. You can only transfer about 675 inputs out at at time, which is about $1 in BTC after fees. You spend your time selecting inputs and waiting for the wallet to manage the enormous amount of inputs. By sending BTC you are feeding the test and delaying transactions. Edit: Corrected Fee that was off by a decimal point. And has now increase to .0000483. |
|
|
|
edit: maybe they should test DASH also? - we ready for some thing like this?
Our blocks would fill up the same and the attack could be performed with less transaction charges incurred, but we have more headroom because we are 4 times more blocks, are more empty than full and there is a flood spike preventative fail safe with instantX that does not need confirming as such but would have to go into the chain at some point. (btw, my record in testnet using IX flooding into only 1 block is 340 transactions using 1 client) Bllock size puts a limit on transactions, but also limits blockchain growth. The questions is what happens to the block chain with millions of transactions. It still isn't close to the point of sale transactions in the trillions. DASH doesn't really look any better than BTC. Transaction size is about the same (1KB) and this is what makes the blockchain bloat when it scales up. See below. For BTCCurrently, bitcoin can only do 2-4 transactions per second. So if 64 million people want to transact in bitcoin, they could only make 1 transaction per year with current block size. If we look at banking transaction, this is what is needed for blocksize for each. US Bank Wires(150 Million transactions) = 1.7MB Swift(international) wires(5 Billion transactions) = 53.3MB ACH(19 Billion transactions) = 202.4MB With the 202.4MB blocksize that would add 29GB to the blockchain each day.
For DASHOK so looking at one of the peak transaction days June 21st. 5K average block size (I assume this is Kilobytes) and 2.75K transactions (I assume 2750 transactions) 5KB/2750 * 576 blocks/day = 1.04 KB transaction size(.001MB) Block size with DASH needed for: US Bank Wires(150 Million transactions) = 0.74MB Swift(international) wires(5 Billion transactions) = 24.7MB ACH(19 Billion transactions) = 93.9MB Now lets look at the ACH transactions with DASH. 93.9MB X 576 blocks/day so daily add to the blockchain is 54GB. We need to find a way to cram more transactions in less data, cutting out old transactions, or doing something Dashingly smart. I don't agree with your calculation, but I like the all inclusive idea of capturing every transaction on the planet. so using 1k as the average transaction size and extending:- Total transaction size per day = [(.150 + 5 +19)*10^9] * 1024 =24.7 terrabytes per day ! if 576 blocks per day, that would mean every block size = 24.7 * (10^12) /576 = 42.9 gigabytes per block required !! assuming 1 block= 1MB, 42.9 GB / 0.001 GB =42882 scalability factor required for entire transactions= 42882 times size reduction !!! (and with 1 as yet unpruned transaction = 1024 / 42882 = 0.024 Bytes long) It could be possible if a secondary master records database was created, the same addresses were used, scrubbing the empty addresses and with a limited number of new replacement addresses ? ... I see what you did there. Totaled up the bank and wire transactions. Actually, those numbers were based on yearly transactions. That's about 365x too much. On the other hand this is probably pretty close for all point of sale transactions when you include credit cards, cash, etc. I agree, there needs to be a scrubbing done. Maybe the standard blockchain includes only latest transactions. So basically, when you update your client it deletes the old stuff as it downloads the new stuff. There would need to be some way to store old data to get clients updated, so maybe the masternodes store the monster blockchain and then compress it with the Evan Almighty Algorithm. |
|
|
|
edit: maybe they should test DASH also? - we ready for some thing like this?
Our blocks would fill up the same and the attack could be performed with less transaction charges incurred, but we have more headroom because we are 4 times more blocks, are more empty than full and there is a flood spike preventative fail safe with instantX that does not need confirming as such but would have to go into the chain at some point. (btw, my record in testnet using IX flooding into only 1 block is 340 transactions using 1 client) Bllock size puts a limit on transactions, but also limits blockchain growth. The questions is what happens to the block chain with millions of transactions. It still isn't close to the point of sale transactions in the trillions. DASH doesn't really look any better than BTC. Transaction size is about the same (1KB) and this is what makes the blockchain bloat when it scales up. See below. For BTCCurrently, bitcoin can only do 2-4 transactions per second. So if 64 million people want to transact in bitcoin, they could only make 1 transaction per year with current block size. If we look at banking transaction, this is what is needed for blocksize for each. US Bank Wires(150 Million transactions) = 1.7MB Swift(international) wires(5 Billion transactions) = 53.3MB ACH(19 Billion transactions) = 202.4MB With the 202.4MB blocksize that would add 29GB to the blockchain each day.
For DASHOK so looking at one of the peak transaction days June 21st. 5K average block size (I assume this is Kilobytes) and 2.75K transactions (I assume 2750 transactions) 5KB/2750 * 576 blocks/day = 1.04 KB transaction size(.001MB) Block size with DASH needed for: US Bank Wires(150 Million transactions) = 0.74MB Swift(international) wires(5 Billion transactions) = 24.7MB ACH(19 Billion transactions) = 93.9MB Now lets look at the ACH transactions with DASH. 93.9MB X 576 blocks/day so daily add to the blockchain is 54GB. We need to find a way to cram more transactions in less data, cutting out old transactions, or doing something Dashingly smart. |
|
|
|
I would bet crypto will come sooner than you think. The financial markets are very unstable with enormous amounts of debt. Once central banks loose control, the whole system could 'collapse' and cause credit to dry up. Crypto and Metals will be the only trusted money and will start to take off.
We will see more Circle like banks that show your balance in dollars, but hold BTC or another crypto. These will bridge through this transition to crypto. Once BTC transactions start to get tracked and people start to get it, DASH will own the space. It will be a DASHtastic future in no time.
Perhaps a combination of your analysis and mine is on the cards. We may get the odd "jump" in adoption into crypto, where something gives way from time to time. That December 2013 rise didn't seem to take much - happened in a month - and technologically we're further down the line now. Bitcoin hasn't been "broken" yet and Dash inherits much of its "rights of passage" valuation, so I'm not saying there are not interesting times on the cards. I'm constantly amazed at the diversity of opinion there is amongst financial commentators on the prospects for the system though. You get you're Gerald Celente's on the one hand predicting "guaranteed" 20% corrections by Christmas, then you get people for whom everything seems just rosy and as it should be and it's a "great time to buy". Perhaps. I still think it will be fear of problems with the existing system to push people over the edge. A bail-in or credit cards not working would sure speed things up. Celente repeats a lot of what he says. He predicts so many things, he is bound to be right a few times. LOL. The Alex Jones sky is falling, buy my supplements. Peter Schiff - gold will be your savior.(although he takes bitcoin). Max Keiser - Bitcoin to $10,000 last year, nope. Steve Quayle - fallen angels will come upon us, stock up on food. Not saying there isn't some truth from all of them. And really, I am just trying to be funny here, no ill intent to any of these guys. It is good to get a wide variety of opinions. And yes I need a conspiracy theropist now. Lol. And for the best market forcaster, Greg Manarino. He called the top of the market a few weeks ago. Now he is calling the triple moving average cross(The market death cross). https://m.youtube.com/watch?v=vIQdATQXtcY |
|
|
|
We are entering a bit of a strange phase in crypto.
Consolidation has taken place - last year saw huge amounts of jostling for position in the various "spaces" followed by a fairly settled market and technology landscape. The only major new arrival is Ethereum but that's been anticipated for over a year anyway.
Against that has been the total anti-climax of bitcoin's market performance. Everybody thought it would have hit multiples of 4 figures by now and it hasn't and doesn't look like doing so anytime soon. Andreas Antonopolis "this is a 3 year project" remark is now two thirds of the way to expiry and adoption looks farther away than ever to me.
The question is what's going to happen now ?
The whole blocksize debacle shows that things are still in their infancy so we may be a few years off the point where mainstream markets actually regard cryptocurrencies as a serious asset - whatever its level of technical integrity.
On the other hand, the fact that marketcaps have been sustained this long is a major achievement. The longer they go on the most of a grip they'll have. Also, the fiat world is kind of starting to teeter. China stalling, QE not working in kickstarting economies and stocks now starting to reflect that.
To me it looks like a 2-10 year affair for crypto to make a significant dent in the world economy.
With that in mind, ED is approaching the end of his 2-year contract (or is it halfway through ? - can't remember) but Dash now has an immensely powerful facility in place to sustain its development and maintenance over that period of mainstream penetration. I think that getting the priorities right for short and medium term will be crucial to success from now on.
I would bet crypto will come sooner than you think. The financial markets are very unstable with enormous amounts of debt. Once central banks loose control, the whole system could 'collapse' and cause credit to dry up. Crypto and Metals will be the only trusted money and will start to take off. We will see more Circle like banks that show your balance in dollars, but hold BTC or another crypto. These will bridge through this transition to crypto. Once BTC transactions start to get tracked and people start to get it, DASH will own the space. It will be a DASHtastic future in no time. |
|
|
|
|
Some comparisons of DASH vs Bitcoin metrics for those interested. Thanks to Sub-Ether for the TAO ratios. Note that the two most meaningful numbers here are the blockchain growth and TAO as these affect usability and bandwidth.
I would bet the TAO ratio is more dependent on internet speed. The blockchain download speed of 1MB/S is about 8Mbps. That approaches the entry level 8Mbps or 10Mbps speed offered by ISPs and could be the limiting factor in updating.
DASH Metrics DASH Bitcoin
Average Transaction Size 1 0.85 KB
Average Transactions per Day 1500 110000 Transactions/Day
Blockchain Size 1.4 47 GB
Blockchain Growth 1.5 93.5 MB/Day
Blockchain Update Speed/hr blocktime(TAO) 0.15 4.14 Sec/Hr
Blockchain Download Speed 0.417 0.941 MB/Sec
|
|
|
|
Another good episode is Let's Talk Bitcoin! #241 - The 'Big Blockist' Perspective https://letstalkbitcoin.com/blog/post/lets-talk-bitcoin-241-the-big-blockist-perspectiveAdam talks about the block size and puts it into perspective based on transactions available. Currently, bitcoin can only do 2-4 transactions per second. So if 64 million people want to transact in bitcoin, they could only make 1 transaction per year with current block size. If we look at banking transaction, this is what is needed for blocksize for each. US Bank Wires(150 Million transactions) = 1.7MB Swift(international) wires(5 Billion transactions) = 53.3MB ACH(19 Billion transactions) = 202.4MB Thinking about the 202.4MB blocksize? That would add 29GB to the blockchain EACH DAY. Almost the entire size of the bitcoin blockchain today. Now to figure out how DASH does with this same metric. What is the average transaction size? I looked at a raw transaction and it had 3500 characters without spaces. Assuming a character is a byte then this size is 3500bytes. /1024 to convert to KB = 3.4KB Am I close on this? block size: https://bitinfocharts.com/comparison/size-dash.htmlnumber of txes per day: https://bitinfocharts.com/comparison/transactions-dash.htmlnumber of blocks per day: https://chainz.cryptoid.info/dash/#!overview (number of blocks per day) x (block size) / (number of txes per day) EDIT: wrong chart, fixed  Wow that was fast. Thanks UdjinM6. OK so looking at one of the peak transaction days June 21st. 5K average block size (I assume this is Kilobytes) and 2.75K transactions (I assume 2750 transactions) 5KB/2750 * 576 blocks/day = 1.04 KB transaction size(.001MB) Block size with DASH needed for: US Bank Wires(150 Million transactions) = 0.74MB Swift(international) wires(5 Billion transactions) = 24.7MB ACH(19 Billion transactions) = 93.9MB Now lets look at the ACH transactions with DASH. 93.9MB X 576 blocks/day so daily add to the blockchain is 54GB. It looks like the heavier transaction days have smaller transaction sizes. So maybe there is an improvement with higher transaction rates. Going this direction though, it looks like we should be optimizing transaction sizes or pruning off old blocks to scale this up. |
|
|
|
Check out the latest Let's Talk Bitcoin podcast "EB94 Gavin Andersen". It talks about the block size debate and details about the little bit of bitcoin governance. https://letstalkbitcoin.com/blog/post/epicenter-bitcoin-94-gavin-andresen-on-the-blocksize-and-bitcoins-governanceCouple quotes. (paraphrasing) Gavin: There are currently no systems of decentralized governance. Ah, I know of one....
Gavin: There are 3 full time developers getting paid to work on Bitcoin. Crazy to see only 3 people maintaining a 3.3 million dollar marketcap coin. DASH with only 1/235th of that size has a blockchain that can pay about 1 full time developer directly. If DASH were at Bitcoin's size it could fund 235 full time people. Now that is progress!
Gavin: I don't think it is a good idea to change to a variable block size vs a halving every 4 years. Hmm. I guess we will see the pain with this next year during the Bitcoin block halving. Half the miners will need to stop, or the Bitcoin price will need to double overnight. Glad DASH changes with a minor 7% change every year. Really? Really? Kind thoughtful words from a BTC developer? My heart melts! Thanks Mr. Anderson for finally looking at this project with an open mind! Gavin only said the underlined stuff. My comments are under his. |
|
|
|
Another good episode is Let's Talk Bitcoin! #241 - The 'Big Blockist' Perspective https://letstalkbitcoin.com/blog/post/lets-talk-bitcoin-241-the-big-blockist-perspectiveAdam talks about the block size and puts it into perspective based on transactions available. Currently, bitcoin can only do 2-4 transactions per second. So if 64 million people want to transact in bitcoin, they could only make 1 transaction per year with current block size. If we look at banking transaction, this is what is needed for blocksize for each. US Bank Wires(150 Million transactions) = 1.7MB Swift(international) wires(5 Billion transactions) = 53.3MB ACH(19 Billion transactions) = 202.4MB Thinking about the 202.4MB blocksize? That would add 29GB to the blockchain EACH DAY. Almost the entire size of the bitcoin blockchain today. Now to figure out how DASH does with this same metric. What is the average transaction size? I looked at a raw transaction and it had 3500 characters without spaces. Assuming a character is a byte then this size is 3500bytes. /1024 to convert to KB = 3.4KB Am I close on this? |
|
|
|
Check out the latest Let's Talk Bitcoin podcast "EB94 Gavin Andersen". It talks about the block size debate and details about the little bit of bitcoin governance. https://letstalkbitcoin.com/blog/post/epicenter-bitcoin-94-gavin-andresen-on-the-blocksize-and-bitcoins-governanceCouple quotes. (paraphrasing) Gavin: There are currently no systems of decentralized governance. Ah, I know of one.... Gavin: There are 3 full time developers getting paid to work on Bitcoin. Crazy to see only 3 people maintaining a 3.3 million dollar marketcap coin. DASH with only 1/235th of that size has a blockchain that can pay about 1 full time developer directly. If DASH were at Bitcoin's size it could fund 235 full time people. Now that is progress! Gavin: I don't think it is a good idea to change to a variable block size vs a halving every 4 years. Hmm. I guess we will see the pain with this next year during the Bitcoin block halving. Half the miners will need to stop, or the Bitcoin price will need to double overnight. Glad DASH changes with a minor 7% change every year. |
|
|
|
sorry not the wallet.
the source code that makes pools pay zero to masternodes
Oh, you may have missed it, but enforcement is on. No worries. |
|
|
|
|
So is there a ransom to fix the code or something?
|
|
|
|
WOW! Fantastic job.
Suggestion:
- By now, you’ve probably heard of Bitcoin, the first widely accepted cryptocurrency. Now it’s time to learn about DASH, which takes Bitcoin to another level by focusing on privacy and speed.
Thanks! We need all suggestions - as we preparing 1 more video " Dash is the best alternative to Bitcoin" at the moment. Please join everybody who can help to produce 1 more perfect video! alex-ru, I would be happy to add several suggestions for the new video. Would you mind opening a new subject on dashtalk.org with the "Dash is the best alternative to Bitcoin" title? |
|
|
|
Let me present our first unofficial DASH Promo video in English language (produced by common efforts) "Dash = Digital Cash" You can view and download it in several resolutions, up to full-HD (1920*1080). It is based on my Russian video, but was improved a bit and adopted for English (western) Audience. English Transcrypt: ... Great thanks to oaxaca - who became the main initiator of this project.He has not just adopted text, but also acted as Voice Talent for this video! Aslo he helped with music. Thanks for tungfa, kot and all others who helped created the best text. Thanks for Otoh who donated big part of this video production. Thanks for further donations - they will help to compensate direct expanses, adopt to other languages, and produce additional videos! DASH: XxG6WRPA5ef767m37eEbGjK8T1UPAVGdCq WOW! Fantastic job. Suggestion: - By now, you’ve probably heard of Bitcoin, the first widely accepted cryptocurrency. Now it’s time to learn about DASH, which takes Bitcoin to another level by focusing on privacy and speed. |
|
|
|
I set this up to run every 10 minutes, just because it will be a pain if you are updating and every minute it tries to restart dashd. If you want to run with UdjinM6's suggestion with the crontab start with a */10 for 10 minutes so you don't have to stop the crontab everytime you update your node.
Why not just put "rm dashd" as the first line of your update script? Basically pull the rug out from under the crontab, so that it will not be able to start up again while you're in the process of updating. Once you've put an (updated) dashd back in the same spot, the crontab should continue to work its magic as usual. The questions are: How long does it take to shutdown dashd? and How fast can you remove the dashd after it is shutdown? If it takes 30 seconds you have a 50/50 shot with a 1 minute restart. I think we do have about an hour that you can be down before you have to to a local start. So every 10 minutes isn't really a big deal. The best way to control dedicated cron jobs like this is through an intermediary file. */1 * * * * [ -f /home/dashuser/.dash/dashd_enable ] && /home/dashuser/mn_watch.sh >/dev/null 2>&1 Then you can ignore cron and just do touch ~/.dash/dashd_enable to monitor/auto-restart and when you want cron to keep its mitts off your procs. -- Also, adding logging-on-action to mn_watch.sh and redirecting to a logfile is a good idea. You want to know how often this happens. #!/bin/bash
if [ -z `pidof dashd` ]; then
echo "$(date +%Y-%m-%d\ %H:%m:%S\ %Z) - restarting dashd"
/home/dashuser/dashd 2>&1 >/dev/null
fi (dashd >/dev/null not a big deal, it has it's own logging) then */1 * * * * [ -f /home/dashuser/.dash/dashd_enable ] && /home/dashuser/mn_watch.sh >/home/dashuser/mn_watch.log 2>&1 Instead of removing the dashd_enable, just move it like this. Create two scripts. One to stop and one to start. stop.sh mv dashd_enable dashd_disable start.sh mv dashd_disable dashd_enable |
|
|
|
I would suggest adding a tools section outside of the V12. There are also some update scripts in the masternode guide section that could go in that tools section too. Thanks. |
|
|
|
I set this up to run every 10 minutes, just because it will be a pain if you are updating and every minute it tries to restart dashd. If you want to run with UdjinM6's suggestion with the crontab start with a */10 for 10 minutes so you don't have to stop the crontab everytime you update your node.
Why not just put "rm dashd" as the first line of your update script? Basically pull the rug out from under the crontab, so that it will not be able to start up again while you're in the process of updating. Once you've put an (updated) dashd back in the same spot, the crontab should continue to work its magic as usual. The questions are: How long does it take to shutdown dashd? and How fast can you remove the dashd after it is shutdown? If it takes 30 seconds you have a 50/50 shot with a 1 minute restart. I think we do have about an hour that you can be down before you have to to a local start. So every 10 minutes isn't really a big deal. |
|
|
|
.......
Actually, crontabs may require a restart or server reboot. Might also need to run with sudo crontab -e if running server as root.
..A server I rented didn't have crontab installed so this isn't always a no brainer...
If you don't have crontab installed, try this: apt-get update
apt-get upgrade
apt-get install cron Then you need to reboot for the cron process to take effect. Add your crontab with crontab -e or sudo crontab -e Then activate your crontab. I think sudo service cron restart Then to stop you need to edit the crontab and then restart the cron service. Seems more complicated to me. I don't think so snip UdjinM6, I do believe the crontab method is indeed the most stable way of doing this and this should work. I am probably thinking this is harder than it is. But I have struggled in the past to get permissions of the crontab user, file permissions, and directory just right so everything runs. Just trying to save someone else a little of that time I wasted... |
|
|
|
|
Show Posts
