I still have another world record you can try for....good luck!
haha, funny QR scan code record, thats original  Is it possible to use my 8 inch telescope with 300 times 8-24 mm Hyperion zoom lense and light noise filters or is that considered cheating ? That would bump you up to the 'with the aid of a lens' category.  For reference the QR code was on a 42" tv run by a raspberry pi. I didn't have any more wall space to backup, but my phone had more capability. You can also generate a QR code with additional error correction, so to really max out this distance you need to max out the error correction setting when making the QR code. |
|
|
|
DASH has an advantage
Just on a point of trivia, Solar, you are no longer the world record holder, check your signature, you will have to surpass 10 million and 1 key pairs if you want the flowery blue ribbon back  LOL, how long did that take? haha, glad you asked, 8 minutes startup time for that many key pairs is pretty impressive eh. ''Initial key pair creation time = 4 hr 53 mins, wallet size = 6.3 GB, RAM used = 2.4 GB, and startup time = 8 minutes'' To put that in perspective. That is like making a new address for every transaction on the bitcoin network as fast as the maximum transaction speed of 5 transactions/sec for 23 days straight. Or in other words, that wallet has enough addresses to receive every single transaction on the bitcoin network(assuming 80% full blocks) for a month. |
|
|
|
DASH has an advantage
Just on a point of trivia, Solar, you are no longer the world record holder, check your signature, you will have to surpass 10 million and 1 key pairs if you want the flowery blue ribbon back This is a true statement...I now hand the blue ribbon back to you, the rightful owner. I still have another world record you can try for....good luck! |
|
|
|
Happy New Year Guys
I'm creating an infographic and would like somebody to read over the following and tell me if it's accurate.
Thank you
Bitcoin can be received instantly, but until transactions are confirmed by the network they can be easily double spent. This means somebody can send Bitcoin to a retailer they are paying and at the same time send those same bitcoins to themselves.
By the time the retailer realises they have not been paid (at least 10 minutes later), the shopper has gone.
This is why you should never trust a zero confirmed Bitcoin transaction and it's also why Bitcoin will never be used (without a centralised third party insurer) like cash at offline retailers, vending machines, train stations, taxis, Gas Stations, cinema's and anywhere else you have instant, secure validated transactions.
DASH has solved this major flaw in Bitcoin...
Don't retailers allow for the odd loss with double spending on zero confirm as a necessary evil, the kicker is that any large transactions need 1 confirmation at least, so small transactions that incur relatively high charges/user time and bloat the blockchain will be way laid due to the inevitable higher fees that must be introduced in order to counter the lack of scalability, after all when the memory pool has 20,000 unconfirms waiting to go into a block, do you really want to wait until tomorrow morning to get 1 confirmation? The point also is that instantX is not random, it is instantly locked where as block entry into a bitcoin block is unpredictable to say the least, is that really how businesses can work? I don't think retailers understand this. They don't plan for double spends at all. And for the most part, people spending Bitcoin are honest enough not to try a double spend. Once it is obvious how big of an issue the double spend problem is, they will just stop using Bitcoin. Then the transaction fee comes up. If you need a 1 block confirmation, you are spending the highest of fees ~$.20. Maybe ok for a large purchase, but a vending machine looks pretty silly when you spend 20% of your Bitcoin on fees for a $1 soda. For a payment over the internet, fees the block confirmations are not a big deal. Shipping is usually $5 anyway, and a 30 min delay for a block isn't a big deal. Privacy is still a concern, but there are options for mixing. Bitcoin may survive on internet sales, but point of sale is out. No matter how many band-aids they use, it just isn't possible. |
|
|
|
Happy New Year Guys
I'm creating an infographic and would like somebody to read over the following and tell me if it's accurate.
Thank you
---------------------------------------------
DASH Solves Bitcoins instant Transaction Double Spend Problem
Bitcoin can be received instantly, but until transactions are confirmed by the network they can be easily double spent. This means somebody can send Bitcoin to a retailer they are paying and at the same time send those same bitcoins to themselves.
So which payment becomes valid (known as confirmed), the payment to the retailer or the payment back to themselves?
The way bitcoin works is that transaction messages are sent to the Peer-2-Peer network when a transaction is initiated. So to double spend all somebody has to do is send one transaction message to spend xyz bitcoin with a zero transaction fee (the payment to the retailer) to one node in the network and at the exact same time send another transaction to spend xyz bitcoin with a transaction fee (the payment to themselves) to another node in the network. To the retailer, it looks like they have received the payment and they allow the shopper to walk away with the goods...
...the problem the retailer can't see (but will become obvious 10 minutes later) is the Bitcoin network has a conflict and the way it solves this conflict is very slow and allows the shopper to leave. Bitcoin resolves the conflict by validating the transaction in a block (a collection of transactions). Unfortunately the block can only accept and confirm a finite number of transactions every 10 minutes. Because there are usually more transactions than a block can hold, only certain transactions get accepted into the block. Guess which transaction gets into the next block? that's right, the transaction with the larger fee (the transaction sent back to themselves). So the transaction back to shopper is validated as a genuine transaction on the network and the transaction the retailer thought they had received on their device suddenly vanishes.
By the time the retailer realises they have not been paid (at least 10 minutes later), the shopper has gone.
This is why you should never trust a zero confirmed Bitcoin transaction and it's also why Bitcoin will never be used (without a centralised third party insurer) like cash at offline retailers, vending machines, train stations, taxis, Gas Stations, cinema's and anywhere else you have instant, secure validated transactions.
DASH has solved this major flaw in Bitcoin...
Instead of validating transactions every 10 minutes like Bitcoin, DASH validates transactions in real time on it's 2nd tier masternode network and if there are two conflicting transactions, both transactions are instantly rejected by the network. This means merchants can be assured that when their DASH wallet says they have received DASH, it really is theirs and will never suddenly vanish.
Dash part needs a change DASH has an advantageDash confirms transactions in blocks in a similar manner to Bitcoin but every 2.5 minutes. In addition, it has a 2nd tier network that can capture the transaction and lock the funds for 5 blocks while rejecting any double spend attempts during this time. This technology is called InstantX and makes Dash the true replacement for cash in point of sale purchases |
|
|
|
OK, I'll say it, as no one else seems to want to... It's painfully obvious now that we were victims of a P&D. Not that it matters long term, but still frustrating. We still have a long way to go. Bitcoin dropped by about $25 so Dash got a bump for all those comparing BTC/Dash. Also the end of the year is upon us, smart people may be planning ahead and using their Christmas bonuses for some Dash. Or more likely planning to purchase by year end for accounting reasons. Either way, we are still up so we are victims of a pump(without dump) due the efforts put in by all of us. I suggest we keep doing what we are doing. Glad to be part of the excitement. Happy New Year. |
|
|
|
Time to support independent creative projects. Ladies and Gentlemen, may I present: The Instantx Soda Machine!  The plan is cunning and clever. We give away paper wallets to BTC Miami attendees with enough DASH to cover the price of a soda with some left over to keep. They load it into their moile wallet, step up to the machine, follow the simple instructions, and behold the power of instantx while chugging a tasty beverage. This project could use your support. Be sure to say nice things and if you are a masternode owner, be sure to vote for funding for this most awesome proposal. mnbudget vote-many 7cc32a7b4bf9f95d56b2a42cf117b517d1de662f2a31480352171089d87b19a5 yes No offence man, but if the machine ends up looking like a hack job in the end, we should avoid it.. The machine will be repainted and professional graphics will be added. We want this to look top notch when we are done. |
|
|
|
Question: how will they obtain a mobile wallet? It's not like it's just sitting in the App Store, after all.
It's being addressed. I hope. We are going to be android friendly, which has an app just sitting at the Google play store(just needs some love to get IX going and is in process). I have asked QuantumExplorer about the apple wallet, but chances are not good for an app store IX version. There might be some phone loaning going on too....we will make due with what works. |
|
|
|
There nothing to stop a rogue vending machine from charging you $10,000 for a coke and the user not noticing. Maybe thats the bigger challenge than sending change.  To avoid rogue machines and other scams from taking a lot more than the listed price, would it be a good idea for the user to be able to set a DASH limit per transaction within their wallet. 10 - 20 DASH would be ideal as this would be adequate for most everyday transactions and if the user knows they need to transact a greater amount they could log into their wallet and manually increase the limit, then lower it again once they have made the large transaction. I think this would be another great safety feature of DASH. Edit: this would also be a good feature for parents who supervise their children's wallets i.e. a daily, weekly or monthly limit could also be set I would rather have 2 passwords. Maybe a pin for small stuff and a longer password/fingerprint for the larger transactions. This still doesn't stop an attacker from emptying your wallet with lots of small transactions, it just limits an accidental spend. For a desktop wallet the best option is to request a code with authy or phone text confirmation. |
|
|
|
... can't refund...
#2 Change from the default nondarksend to darksend. not so. we can refund darksends too. the same input lookup works for all transaction types. (we have inputs to send to, we just don't know their history.) Time to get technical....Let's go. Of course, the fee for the darksend is rounded up. So a .41 Dash beverage is actually .5 dash with the .09 Dash fee. And the fee actually passes on to the receiver if I am not mistaken. There would be 5 inputs of .1 in the transaction. Likelihood of all of them originating with the sender wallet = slim. So the refund would most likely be a partial refund. Maybe hitting a 20%-40% return rate. You are misinformed. Darksend doesn't work that way. But, I understand why. The terminology is confusing. Darksend (the transaction checkbox) just spends from your pre-mixed inputs. There is no other transaction involved. I can choose any input for a refund and you get all your funds back. Darksend Mixing (the ahead-of-time masternode input shuffling) is the only time another users inputs are involved in a merged transaction. You're always sending to yourself in this mode, never a third party. It is times like this when I am thankful to know people smarter than me. You, moocowmoo are one of them. Ok, time to play on testnet for a while and check this out. |
|
|
|
I love when I go to watch a movie and my investment increases by $2,000. I wonder how Otoh feels right now? Seriously, though, fantastic job to you guys, and for keeping it a secret for so long. Miami is going to be fun!
Thanks. I have had fun dropping hints. Camosoul just picked up the machine last night. I didn't want to jump the gun until it was a solid go. We are getting close to Lincoln Day when Dash passes the $5 bill. |
|
|
|
... can't refund...
#2 Change from the default nondarksend to darksend. not so. we can refund darksends too. the same input lookup works for all transaction types. (we have inputs to send to, we just don't know their history.) Time to get technical....Let's go. Of course, the fee for the darksend is rounded up. So a .41 Dash beverage is actually .5 dash with the .09 Dash fee. And the fee actually passes on to the receiver if I am not mistaken. There would be 5 inputs of .1 in the transaction. Likelihood of all of them originating with the sender wallet = slim. So the refund would most likely be a partial refund. Maybe hitting a 20%-40% return rate. |
|
|
|
I also think the vending machine idea is a great example of the power and versatility of instantly confirming crypto. It's a fantastic initiative. But I can see some banana skins that you might want to think about before rolling it out to a public demo. First of all, this: If a darksend transactions without exact amount is sent, it keeps the change. ...I don't think that's acceptable because it isn't commercially consistent and basically amounts to theft. Think two 13 year old teenage kids with iPhones who buy a coke. One gets change and one doesn't cos they're not technologically nerdy enough to check their denominations ? They don't really want to be faced with questions like "Darksend" "Not Darksend". It might as well be two different currencies. Further, if change is involved, it should be on condition of supply of a change address, not the on condition of coin denominations. That way the service can be commercially consistent and also optimally serve instances of homogeneous denominations as your current design does. (Because it supplies an implicit change address, but heterogeneous payments then need the option of supplying an explicit one). It depends on amount you send. Transaction comes from few addresses. Denominations like 0.1, 1.0, 10 are in different addresses.
I'd just ditch the whole idea of change since it isn't really compatible with cryptocurrency (other than change addresses in wallets where the wallet itself has full control over everything). Just accept exact amounts otherwise no coke - since it's far easier for a customer to type the right amount into their wallet than be worrying about how their payment was denominated. Doesn't the QR code do that for them anyway ? Sorry to be so nerdy about this but it's a great idea and I don't want you to get shot down by a*ssholes (other than me  ) who home in on the glaring banana skins of the concept only to ignore the huge potential of it. Also, what you're demonstrating isn't really a vending machine, it's a metaphor for an entire commercial business model so it's the commercial priorities that need to be thought through, not the blockchain technicalities. In that regard, details like that change thing can explode in your face when presented to the "wrong" audience. Like Moocowmoo said, we will imbed the price in the QR code. They would actually have to modify it for there to be change. But I figure there will be 'testers' that will try this to see what happens - most likely they will all be in Miami on the 21st. So we want to not only show them what is possible but to make it more possible than they thought it could be! You need to do both of these things to not get your change back: #1 Change the amount. #2 Change from the default nondarksend to darksend. It is unlikely for a novice to do this. We will also put a number to contact with problems just like if you got your $1 bill stuck. It should also be obvious that when sending a darksend transaction it shouldn't be possible to return funds(it is an anonymous transaction). In production, the machine could have a camera to grab a return address QR code, but we are pretty far down on the what ifs. The change return is a cool feature and one that can really be useful for other scenarios. (like a gas station when you don't know how much you want before you fill your tank) It is already working too. Here is proof from a transaction on testnet. 15.01 Dash sent (.01 IX fee). 2 Dash Sprite was charged, and 13 Dash returned. This also happened in a split second.(IX acknowledged, change address found from looking up transaction, and then sent back). A lot happened here and it is pretty amazing it is so fast. Moocowmoo did a great job on this.  |
|
|
|
If a darksend transactions without exact amount is sent, it keeps the change.
I don't quite understand this bit. How can the receiving address know if it's a darksend transaction or not ? Darksend is a background mixing process, not a payment action. Surely, at the point of payment, there's no distinction  When you send a payment there is a box for Instantx and for darksend. If you hit the darksend box - no change for you. If you don't send with instantx checked - Instant refund. Yes, you can tell looking at the incoming transaction how these were sent. More detailed answer.Do you remember that bit about darksend transactions being anonymous? Yeah, well it isn't possible to figure out where they come from(or more appropriately, which of the 100 inputs are the senders). There is also no change address to figure out a return address. A non-darksend transaction will always(I think) have a change address we can use to return funds. Moocowmoo made a script that can figure this out in a split second. Really cool. Pille, All running on a little Raspberry Pi 2 ....with 5" display arriving soon. |
|
|
|
^ Is this true? What's the model of the 'soda/pop machine' you use? Please show more than this photoshop  Yes, this is real. Here is another picture. And the machine is a Dixie Narco DNCB 168m.  Wow, you thought I used Photoshop...Thanks. Only Powerpoint was used on that last pic. I figured my post would be tweeted, so I wanted to make it look closer to a finished product. We (as in Camosoul) have a lot of work to make it look like my last picture. |
|
|
|
And here is what we have been working on for the Miami show..... Yes, a Dash Instantx detecting, soda/pop machine. Why a vending machine? Because it shows off InstantX in a real use point of sale scenario. This can't be done with any Bitclone(coins that confirm and secure transactions at the same time). We have a machine(Thanks Camosoul), we are almost done with software(Thanks Moocowmoo), graphics are started(Thanks Raptor73), and will be adding android wallet instantx functionality(Thanks Fulltimegeek). Camosoul, Moocowmoo, Fulltimegeek, Splawik21, Oaxaca, Raptor73, and Solarminer(The Instigator) are all helping on this. What does it do?- Displays a QR code to send Dash.
- If the amount is sent via Instantx and the amount is equal or above the amount needed, it sends the command to credit the machine for 1 beverage. This is fast - Instant from a human's perspective.
- If the amount is less/over, it instantly returns the change.
- If a darksend transactions without exact amount is sent, it keeps the change.
- If a standard transaction is sent it rejects it and instantly sends it back. (Maybe display "We don't wait for block confirmations and either should you, InstantX instead!")
- Once a purchase is made, it displays a thank you and rotates the QR code.
This is just a stepping block. Next we plan to convert gas pumps, which is why returning change is important. And many other uses, only possible because of InstantX.
|
|
|
|
Nice comment by Pinkfish too. |
|
|
|
Get notified on new budget proposals!We implemented a new feature to allow immediate notification (email, mobile phone or slack) in case a new budget proposal pops up. You need a Dashwhale.org account to use this feature. You don't have to enter any masternode data to use it. Just enable the proposal notifications at the section "My Account" => "Notifications" => "Edit notification". https://www.dashwhale.org Great work. Thanks! I would suggest the notify budget proposal is checked as a default when creating notifications. |
|
|
|
Add a script to start every 2 minutes. Start crontab editor here: (choose nano if it asks) Add this line at the bottom (change home/dash for your install) - make sure you add a return at the end. */2 * * * * /home/dash/dashwhale-updater/dwupdater control x y enter to save Might as well add this line as well to cover reboots as well as every X minutes: @reboot /home/dash/dashd -shrinkdebugfile Hmmm. I have been thinking it would be advantages to restart dashd every 2 days. They start to use more memory after a day. Maybe do this. Is that too much for a crontab? * * /2 * * /home/dash/dash-cli -datadir=/home/dash/.dash stop && sleep 30 && /home/dash/dashd -datadir=/home/dash/.dash -shrinkdebugfile |
|
|
|
Could someone possibly prove themselves to be a thoroughly good egg and share that dashd checker/re-starter script please.
I gave up on my own and now just use the Dashwhale V4 script. It checks if dashd is running, then checks if it is responding. If it doesn't respond it kills it and starts it again. Dashwhale logs the error and sends an email on warnings, errors, and restarts. Register with dashwhale.org, get your api, and add your masternode if you want monitoring, Download and unzip with this command: wget https://www.dashwhale.org/downloads/dashwhale-updater-v4.tgz -O - | tar -xz Edit with this. Add api and masternode info. nano dashwhale-updater/dashwhale.conf control x y enter to save Add a script to start every 2 minutes. Start crontab editor here: (choose nano if it asks) Add this line at the bottom (change home/dash for your install) - make sure you add a return at the end. */2 * * * * /home/dash/dashwhale-updater/dwupdater control x y enter to save |
|
|
|
|
Show Posts
