|
you guys may be right, but i don't really see it. why just give the money to a payment processor.
additional step to getting funds
could have some security implications
more costly, it could be cheaper to buy one of them php enabled vps a month if you get enough transactions. secuity is not an issue because the coins would only be on there for a short while.
It might be hard to imagine now because there is only 1, maby 2 stable bitcoin wallet manager things.(GUIs to not count because we need a pure php solution or similar, java could work, but php would be best because pretty much all providers have it)
|
|
|
|
|
One of the things i hate about japan is the fucking shit ass retarded law that requires genitals to be censored, drawn or filmed.
|
|
|
|
I don't know if anyone else has this though - I can't be the only one....
Is it that hard to imagine someone setting up a bitcoin processing guarantee service, maybe even as a part of a bitcoin POS solution. The service provider would have a pool of mining power combined with some well-distributed (network topography as well as geographically) bitcoin nodes.
The service provider would aggressively distribute their transactions to the network, as well as watch the network for "suspicious traffic", and give the merchant a red/green light on any given transaction within seconds - less time it currently takes someone to enter their PIN or sign a credit card slip, for example.
The service provider would also guarantee the transaction, in return for a transaction fee above-and-beyond the normal bitcoin transaction fee. Maybe the merchant can choose how long they want to wait, the longer the wait (30 seconds instead of 3 seconds?) the less the fee. Maybe the service provider strikes up a deal with some of the larger mining pools to always take their transactions (even fee-free ones) in return for a slice of the service fee in the event of the pool solving the block.
This provides the merchant with the certainty and speed they need, at a reasonable price compared to the price of processing credit card transactions.
That's just one idea, maybe other people have different ideas...
is the customer giving the money to the payment processor? |
|
|
|
6870 gpu 940mhz  23.5-23.7 Mkeys/s @echo off
oclvanitygen.exe -ik -p 0 -d 0 -o ocl 1
pause |
|
|
|
x86: 800-850 x64: 1300-1350 @echo off
vanitygen64.exe -qik -o file3 1ctoon6
pause pretty good stuff are Mkeys/s 1024 based or just 1000 and are hashes the same way, always wondered 1090T 8gigs of ram windows 7 ultimate x64 |
|
|
|
This has been discussed in detail many times. Waiting is required for online transactions where the buyer is in control of the timing of the transaction and could potentially execute a 51% attack or a race attack. The 51% attack is not as viable in a transaction which takes place in person because the attacker can't control the timing of an in person transaction easily enough, and the race attack is easy to thwart simply by watching network activity for a few seconds. NOTE that this doesn't apply to vending machines.
Im not talking about that, as the 51% attack is silly at best. im talking about sending multiple signed transactions into the network at the same time. i go to walmart, you go to other store. use self checkout when the store is kinda empty. then just send a text to your buddy to push the button at the same time. id imagine in the future you would have a 5 second window to do it. But you just described the race attack! Again, all you have to do is watch the network for a few seconds, as already stated, to see that the coins that were supposedly sent to you were also apparently sent to someone else. i misread your post, you can not watch the network for already existing transactions and always be 100% sure. as the network grows in size it may have unpredictable effects. sure right now you can check easily, but who knows. the store could be compromised over time by an attacker having a bunch of nodes that broadcast normal transactions, but refuses to broadcast ones not in its favor. botnets serve this purpose well and could be rented out for yet another purpose. Are you just thinking out loud (so to speak)? i guess, but you can not know for sure what the future will be. super peers would definitely reduce transaction latency, so it may not be a problem, you can always take gnutella as an example though, as it is very similar. OK. Well, I recommend giving it more thought. For instance, in this scenario the attack requires that both transactions be broadcast, but that the merchant sees one transaction first and the miners see the other transaction first. Refusing to relay doesn't help this attack succeed unless you've somehow successfully separated the merchant from the rest of the bitcoin network. That's where you need not only a botnet, but a lot of luck. How are you going to prevent the merchant's bitcoind from connecting to a bitcoind not in your control, and then seeing what you're up to? If you don't have an "Internet kill switch" then this will be very hard to do. And by this time you've spent far more money than you can rip off Wal-Mart for at the register. Plus, they'll likely figure it out before you get to the parking lot. yes it does depend a lot on luck, but even if only 1/4 of the nodes they connect to are not honest, it would slow down how fast you see transactions. and another factor to consider is volume. right now i estimate we are only seeing less than 1% at most. its probably below .1% of the amount if bitcoin takes off mainstream and is used as real currency. at this point i could see it being more burdensome to propagate all of them, and thus it would be slower. and i would also guess there would be less nodes with ports forwarded too. so sending more data with less nodes could be a problem, not only for race attacks, but the network in general. yes all them numbers are pulled outa my ass, but id guess they are fairly optimistic. |
|
|
|
This has been discussed in detail many times. Waiting is required for online transactions where the buyer is in control of the timing of the transaction and could potentially execute a 51% attack or a race attack. The 51% attack is not as viable in a transaction which takes place in person because the attacker can't control the timing of an in person transaction easily enough, and the race attack is easy to thwart simply by watching network activity for a few seconds. NOTE that this doesn't apply to vending machines.
Im not talking about that, as the 51% attack is silly at best. im talking about sending multiple signed transactions into the network at the same time. i go to walmart, you go to other store. use self checkout when the store is kinda empty. then just send a text to your buddy to push the button at the same time. id imagine in the future you would have a 5 second window to do it. But you just described the race attack! Again, all you have to do is watch the network for a few seconds, as already stated, to see that the coins that were supposedly sent to you were also apparently sent to someone else. i misread your post, you can not watch the network for already existing transactions and always be 100% sure. as the network grows in size it may have unpredictable effects. sure right now you can check easily, but who knows. the store could be compromised over time by an attacker having a bunch of nodes that broadcast normal transactions, but refuses to broadcast ones not in its favor. botnets serve this purpose well and could be rented out for yet another purpose. Are you just thinking out loud (so to speak)? i guess, but you can not know for sure what the future will be. super peers would definitely reduce transaction latency, so it may not be a problem, you can always take gnutella as an example though, as it is very similar. |
|
|
|
This has been discussed in detail many times. Waiting is required for online transactions where the buyer is in control of the timing of the transaction and could potentially execute a 51% attack or a race attack. The 51% attack is not as viable in a transaction which takes place in person because the attacker can't control the timing of an in person transaction easily enough, and the race attack is easy to thwart simply by watching network activity for a few seconds. NOTE that this doesn't apply to vending machines.
Im not talking about that, as the 51% attack is silly at best. im talking about sending multiple signed transactions into the network at the same time. i go to walmart, you go to other store. use self checkout when the store is kinda empty. then just send a text to your buddy to push the button at the same time. id imagine in the future you would have a 5 second window to do it. But you just described the race attack! Again, all you have to do is watch the network for a few seconds, as already stated, to see that the coins that were supposedly sent to you were also apparently sent to someone else. i misread your post, you can not watch the network for already existing transactions and always be 100% sure. as the network grows in size it may have unpredictable effects. sure right now you can check easily, but who knows. the store could be compromised over time by an attacker having a bunch of nodes that broadcast normal transactions, but refuses to broadcast ones not in its favor. botnets serve this purpose well and could be rented out for yet another purpose. |
|
|
|
i think you guys are missing the point. this is not really for online stuff
Wait, so I have to go to some shop's website and buy a voucher before I go to the shop? This sounds inconvenient and unnecessary. yes, but it would be quick and easy. and it helps avoid the very likely situation of everyone dumping their coins on a single website bank thing. this is bad because even if the company does not steal your coins, they still could accidentally delete them or someone could hack into the systems. because the system would be opensource, people could audit the code. Why should I go to all this trouble when I could just spend bitcoins in the shop? you can, but it does not provide any real security for the shop, and the shop may not even accept them without waiting for a block. this is the solution to the problem where you don't want to wait 10 minutes or more for your stuff, and provide security for the shop against double spending. I see the system to be very fair, shops should not have to just accept 0 block transactions. The shop doesn't need to wait for a block if you are paying in person. why not, if they just accept unverified transactions they are asking to get ripped off. This has been discussed in detail many times. Waiting is required for online transactions where the buyer is in control of the timing of the transaction and could potentially execute a 51% attack or a race attack. The 51% attack is not as viable in a transaction which takes place in person because the attacker can't control the timing of an in person transaction easily enough, and the race attack is easy to thwart simply by watching network activity for a few seconds. NOTE that this doesn't apply to vending machines. Im not talking about that, as the 51% attack is silly at best. im talking about sending multiple signed transactions into the network at the same time. i go to walmart, you go to other store. use self checkout when the store is kinda empty. then just send a text to your buddy to push the button at the same time. id imagine in the future you would have a 5 second window to do it. Or maybe we phase out POS purchases completely...
yeah, why dont you go buy a watermelon on ebay and see how that turns out. |
|
|
|
i think you guys are missing the point. this is not really for online stuff
Wait, so I have to go to some shop's website and buy a voucher before I go to the shop? This sounds inconvenient and unnecessary. yes, but it would be quick and easy. and it helps avoid the very likely situation of everyone dumping their coins on a single website bank thing. this is bad because even if the company does not steal your coins, they still could accidentally delete them or someone could hack into the systems. because the system would be opensource, people could audit the code. Why should I go to all this trouble when I could just spend bitcoins in the shop? you can, but it does not provide any real security for the shop, and the shop may not even accept them without waiting for a block. this is the solution to the problem where you don't want to wait 10 minutes or more for your stuff, and provide security for the shop against double spending. I see the system to be very fair, shops should not have to just accept 0 block transactions. The shop doesn't need to wait for a block if you are paying in person. why not, if they just accept unverified transactions they are asking to get ripped off. |
|
|
|
i think you guys are missing the point. this is not really for online stuff
Wait, so I have to go to some shop's website and buy a voucher before I go to the shop? This sounds inconvenient and unnecessary. yes, but it would be quick and easy. and it helps avoid the very likely situation of everyone dumping their coins on a single website bank thing. this is bad because even if the company does not steal your coins, they still could accidentally delete them or someone could hack into the systems. because the system would be opensource, people could audit the code. Why should I go to all this trouble when I could just spend bitcoins in the shop? you can, but it does not provide any real security for the shop, and the shop may not even accept them without waiting for a block. this is the solution to the problem where you don't want to wait 10 minutes or more for your stuff, and provide security for the shop against double spending. I see the system to be very fair, shops should not have to just accept 0 block transactions. |
|
|
|
i think you guys are missing the point. this is not really for online stuff
Wait, so I have to go to some shop's website and buy a voucher before I go to the shop? This sounds inconvenient and unnecessary. yes, but it would be quick and easy. and it helps avoid the very likely situation of everyone dumping their coins on a single website bank thing. this is bad because even if the company does not steal your coins, they still could accidentally delete them or someone could hack into the systems. because the system would be opensource, people could audit the code. |
|
|
|
|
until the price of bitcoin stays with in 10% per month, it wont be a viable currency.
|
|
|
|
Hey, I'm quite new to bitocin so I just wondered: why are they several private keys stored in a wallet.dat? Given what you explained, you only need to know 1 private key, right?  its soposed to give more anonymity. however i find it pointless, and would rather the client just make a new address when requested. |
|
|
|
So let me get this straight. You can create a private key with a passphrase import it into a wallet. Transfer funds to it and then delete the wallet.dat and recover it by repeating the process?
yep |
|
|
|
@Ampirebus
I am assuming the massive pile of sand in your panties that has accumulated is due a thousand other people trying to trade at the same time and some how you think you are the one entitled to trade??
Isn't that basically it?
are you a child or do you just possess the mind of one? The daily volume of the site would lead one to believe the owner could maintain a website that does not take minutes of refreshing to load. If that is your response to a legitimate grievance I question your general sanity and well being. Other than that I have no response because your post does not really dignify anything further. its in gox interest that everyone can place a trade order 24/7 as the way gox makes money is on the trade fees... more trades... more fees... more income... I'm no huge Gox fan by no stretch, but it is the best we have. They are not making a huge sum of money everyday and refer to my previous post, I think it applies. I think they make enough to have a decent setup and separate sets in EU NA and SEA. there is no way you can convince me they dont make at least 20k a month, easily enough for VERY good redundant dedicated hosting in many countries. |
|
|
|
Too big to fail does not exist in Bitcoin.
yet |
|
|
|
|
i dont understand why people constantly buy and sell. don't they realize you pay fees for every transaction? and that if you had 1% of a brain you see that bitcoin goes up and down very unpredictably.
it fuckin pisses me off that people trade bitcoins around like stock.
|
|
|
|
|
if its taking longer than 3 seconds to load a page as simple as mtgox.com, there is a problem.
|
|
|
|
Okay so I have no problems generating a SHA256 hash, personally I would use multiple hash algo's on my passowrd pharse which included a key , then I would Vigenere Encrypt that, or Xor then MD5 hash that and then finally SHA256 the result to generate a custom SHA256 key. now my question is how do I use that generated SHA256 hash in the bitcoin client as a wallet address? I have only just started using the bitcoin client as a wallet since mybitcoin problems. Could someone explain how to use a custom generated SHA256 key as there wallet address in the bitcoin client please?
https://github.com/jackjack-jj/pywallet |
|
|
|
|
Show Posts
