You've made an investment and the longer you hold that investment the better off you will be on your return. If I were you I would ignore the market and only read the news about Bitcoin (not just from one source). Take out only what you need to pay your bills or buy something that you want specifically but try to trade only in BTC without first converting to USD.
He's spent money on mining hardware not coins. He would have been better of had he bought bitcoins with that money.
|
|
|
Fullphp code is given in blockchain only $real_secret = 'ZzsMLGKe162CfA5EcG6j' $invoice_id = $_GET['invoice_id']; //invoice_id is past back to the callback URL $transaction_hash = $_GET['transaction_hash']; $input_transaction_hash = $_GET['input_transaction_hash']; $input_address = $_GET['input_address']; $value_in_satoshi = $_GET['value']; $value_in_btc = $value_in_satoshi / 100000000;
//Commented out to test, uncomment when live if ($_GET['test'] == true) { return; }
try { //create or open the database $database = new SQLiteDatabase('db.sqlite', 0666, $error); } catch(Exception $e) { die($error); }
//Add the invoice to the database $query = "insert INTO invoice_payments (invoice_id, transaction_hash, value) values($invoice_id, '$transaction_hash', $value_in_btc)";
if($database->queryExec($query, $error)) { echo "*ok*"; }
//Select the amount paid into an invoice with select SUM(value) as value from invoice_payments where invoice_id = $invoice_id
Wow awesome! SQL injection heaven!
|
|
|
I don't know why you guys are so negative about this. This is a good thing.
|
|
|
The maximum amount that we will accept as deposit from an user is likely going to be 1 BTC and the minimum amount will be 0.001 BTC. Is this still too small for Blockchain.info? You know you really should do your own searching and reading. The minimum supported transaction size is 0.001 BTC. Forwarding transactions will include a network fee paid by blockchain.info.
https://blockchain.info/api/api_receiveMake of the above what you will.
|
|
|
My largest mistake was indeed to architecture the website without any regard for the needs and preferentes of the early bitcoin users.
Can you explain what you mean by that? It seems to me that you didn't do enough promotion.
|
|
|
I suppose you could have your seeded Electrum wallet under a different user than the one you use for web browsing. The wallet file would then be under /home/different_user/.electrum/wallets/default_wallet. Then you could install a watch only wallet under your normal user.
Of course just moving your existing wallet file is not good enough. You have to send the coins to the new wallet under different_user.
|
|
|
It is possible to use bitcoind then. You can generate addresses using open source php code that I linked to before. To find out about transactions to those addresses you can use bitcoind. Bitcoind has a feature where it runs a command each time it learns of a new transaction. All you have to do is watch for transactions to addresses you've handed out to your customers.
Thanks for your input Abdussamad. Which open source php code did you link to? Are you referring to the following link that you provided? https://bitcointalk.org/index.php?topic=404228.msg4379742#msg4379742The above link shows PHP code for using Blockchain.info, which I already have and want to test.
|
|
|
Thanks for your input. Unfortunately, we do not know Python.
It is possible to use bitcoind then. You can generate addresses using open source php code that I linked to before. To find out about transactions to those addresses you can use bitcoind. Bitcoind has a feature where it runs a command each time it learns of a new transaction. All you have to do is watch for transactions to addresses you've handed out to your customers.
|
|
|
* Coinbase Buyback plugin
Ah this a way to monetize the software? Good. Some money flowing to the devs for all their hard work is good.
|
|
|
The volatility argument just does not fly. You price your products in USD and your refund is also priced in USD at the current market rate. How exactly do these companies deal with foreign fiat currencies? Do they complain about the difference in Euro/dollar rates between now and the time of a refund?
Well I guess the issue would be if I paid 0.1BTC for a 1 year subscription, and I notice that the price of BTC has gone up 10x after 6 months. I will obviously cancel my subscription to get the 0.05BTC at the inflated rate. They need to figure out how to convert the current price, and return the current value of BTC back, so 0.005 back. Just some things to consider. What you are saying doesn't make any sense. You spent 0.1 but cancel to get 0.05???
|
|
|
The volatility argument just does not fly. You price your products in USD and your refund is also priced in USD at the current market rate. How exactly do these companies deal with foreign fiat currencies? Do they complain about the difference in Euro/dollar rates between now and the time of a refund?
|
|
|
It's about as safe as any other Internet connection. The idea is that you don't trust any connection including your home/office one.
|
|
|
TRy specifying a data directory:
bitcoind -datadir=c:\whatever\whatever\ getinfo
|
|
|
The way bc.i works is your browser gets a copy of the encrypted wallet when it visits a page with a legitimate identifier. So aliases make it easy for hackers to get copies of encrypted wallets. All they have to do is run a bot that loops over a dictionary and harvests encrypted wallets en masse. Then they can take their sweet time brute forcing those wallets using their GPU farms. This is how many ordinary users who used simple passwords lost their coins.
So now when you visit an alias you get an email that tells you your wallet identifier and then you login using that.
|
|
|
If it does not allow you to send without fee, probably very high risk of losing the coins exists.
This worries me. Not because I think there is any chance of loosing coins but because you don't know that there is no chance of loosing coins. Spend transactions are either mined into a block or not. If they are not being mined you can just stop broadcasting that transaction and mining pools will eventually forget about it and you can send those coins with a fee. How exactly is there a risk of "loosing" coins, then? Ask the core Bitcoin developers. The code which asks you for a fee in that case has not been changed in my fork. This fork is merely 3 lines of code which turn off a single limitation which forces you to pay a fee even when it is not absolutely necessary. That is not rocket science. You seem to have misunderstood what I wrote. I just said that there is never a risk of loosing your coins just because you didn't pay enough of a fee. You just remove the transaction using pywallet and wait for the mining pools to forget it. Then you can redo the transaction again with a fee. This is not what i referred to. I refrerred to the part of your answer which stated that "it worries you that i don't know that there is no chance of losing coins". Sure I don't know, because I have not studied the Bitcoin-QT code in detail - I didn't need that in order to create my fork. If they are not being mined you can just stop broadcasting that transaction and mining pools will eventually forget about it and you can send those coins with a fee
Are you sure about that ? Won't some other nodes keep relaying the transaction so it will be forever stuck in a limbo ? Is there a time limit for how long a transaction can be kept in memory before it becomes obsolete & is removed ? [Citation needed] Actually i would like to see a citation (or a snippet of code) for that. I don't have time to study the whole code. I don't have a citation for you. It was asked on this forum and I learned from that. nodes aren't fond of keeping around transactions that can't be mined because the fee is too small. The only reason it sticks around is because -qt keeps broadcasting it over and over again in vain. I can tell you that pywallet supports removing transactions from wallet.dat file for this very reason: https://bitcointalk.org/index.php?topic=35214.0
|
|
|
If it does not allow you to send without fee, probably very high risk of losing the coins exists.
This worries me. Not because I think there is any chance of loosing coins but because you don't know that there is no chance of loosing coins. Spend transactions are either mined into a block or not. If they are not being mined you can just stop broadcasting that transaction and mining pools will eventually forget about it and you can send those coins with a fee. How exactly is there a risk of "loosing" coins, then? Ask the core Bitcoin developers. The code which asks you for a fee in that case has not been changed in my fork. This fork is merely 3 lines of code which turn off a single limitation which forces you to pay a fee even when it is not absolutely necessary. That is not rocket science. You seem to have misunderstood what I wrote. I just said that there is never a risk of loosing your coins just because you didn't pay enough of a fee. You just remove the transaction using pywallet and wait for the mining pools to forget it. Then you can redo the transaction again with a fee.
|
|
|
If it does not allow you to send without fee, probably very high risk of losing the coins exists.
This worries me. Not because I think there is any chance of loosing coins but because you don't know that there is no chance of loosing coins. Spend transactions are either mined into a block or not. If they are not being mined you can just stop broadcasting that transaction and mining pools will eventually forget about it and you can send those coins with a fee. How exactly is there a risk of "loosing" coins, then?
|
|
|
All of this crap will only make it harder to a) make backups and b) restore from backups and c) recover backups should you ever forget your passwords. In the end you'll be dissuaded from making regular backups and you'll loose coins, so keep it simple. Use the built in encryption in bitcoin-qt and store your backups offline on removable media like USB drives. Sticking it online is asking for trouble.
Also remember to make new backups once every 100 transactions or you'll loose coins. Alternatively you could switch to electrum and only need to make one backup at the start.
Provided he uses a long password (20+) with numbers, different cases and symbols he should be fine with uploading it, as unless his pass is guessed or hit by a dictionary attack he should be fine with uploading it to an online storage site. Plus it means that if he has a fire or somehow loses all his USBs he can always download a copy of his wallet. Let's see to crack the wallet you need a copy of the encrypted wallet + the password 1. Offline backups mean to get the copy of the encrypted wallet you need to physically visit his residence/office and grab the backup disks. 2. Online backups mean you need to access his cloud account. You can take your sweet time doing this remotely. Phishing attacks would work in this scenario. So IMO 1. is much better. edit: To secure your wallet in your online storage you have to keep a strong password for you wallet file, your storage account *and* your email account because otherwise a thief could use the forgotten password link to get access to your storage account. To secure your offline backup you only need the password for your wallet file and the key to your safe deposit box/storage box whatever where you are keeping your backup media.
|
|
|
|