-Blockchain.info payment receive API-
I highly recommend not to depend on another site when you have an easy (but time consuming) alternative. You should give more importance to security than accessibility. That is correct depending on what site the OP plans on running. If he's selling jars of jelly for $3 each, it's unlikely that he will become a target or have to worry about security. Also where's the security issue with receive payments API? As I recall the times bc.info had issues was with their mobile wallets not generating a random address. The receive payments API uses deterministic addresses based on your receiving address so there's no risk of generating the dreaded "1Bn9ReEocMG1WEW1qYjuDrdFzEFFDCq43F" address. |
|
|
|
Personally I think you should use blockchain.info's receive payments API if you want to create addresses on the fly without running bitcoind. More info: https://blockchain.info/api/api_receiveWhat kind of site are you running and why are they depositing? If you are keeping track of balances you'll need to run a database. If you just want to accept payments for something you can just have them fill out a form with their name. This can be your buy page, save as buy.php <?php
$secret = "1234abcd"; //secret can be anything you want it's intended to prevent hackers trying to spoof your callback
$my_address = "1J9ikqFuwrzPbczsDkquA9uVYeq6dEehsj"; //Replace this with your BTC address, payments will get forwarded here
$username = $_POST['username'];
$callback = "http://yourdomain.com/callback.php?user=".$username."&secret=".$secret; //change to your domain
if(isset($_POST['submit'])){
$response = json_decode(file_get_contents("https://blockchain.info/api/receive?method=create&address=".$my_address."&callback=".urlencode($callback)), true);
$sendPmt = "Send your payment to ".$response["input_address"];
}
?>
<html>
<form method="post"><input type="text" name="username" placeholder="Username"><br><input type="submit" name="submit" value="buy now"></form>
<?php echo $sendPmt; ?>
</html>
Below can be your callback page, save as callback.php. It will send you an email that payment was received and notify blockchain.info it was received by your web server with *ok* <?php
$secret = "1234abcd"; //This needs to match your other secret from the buy page
//checks to make sure secret matches
if($_GET['secret'] != $secret){
echo "Quit hacking hacker!";
return;
}
//send yourself an email to notify that payment was received
$youremail = "youremail@email.com";
$emailtitle = $_GET['user'];
$body = "Invoice paid";
$headers = "From: sales@yourwebsite.com" ."\r\n";
$headers .= "Content-type: text/html\r\n";
$mail = mail($youremail, $emailtitle, $body, $headers);
//notifies blockchaininfo that you received the callback
if ($mail) {
echo "*ok*";
}
?>
There's also this video that might help. https://www.youtube.com/watch?v=vWt9wRZ3Hhk |
|
|
|
Yea everyone should dump their btc and buy some shitcoins. LTC whew! Remember when that was $28 bucks each? How's the order of magnitude drop feel at $1.80  Don't forget to buy that potcoin and dashcoin and all the other unoriginal ripoffs that wouldn't exist if it weren't for BTC. |
|
|
|
Hi guys,
My skills go as far as downloading a wallet and moving coins about.
With this in mind.....
Can someone explain what Gavin is planning to do and how definite it all is?
Side chains etc? Double coins? Wtf?
Thanks in advance.
I'm a little confused too. All I really give a shit about is if my coins are safe in cold storage & if they'll lose value because of this crack pot / dick measuring venture. Anybody explain this in layman's terms about what it means for current bitcoin owners / hodlers & the price / validity of them. I don't care about blocks sizes, forks etc etc. Bitcoin is a long term investment for me I don't need to know the techie science stuff. All that matters to me is the price & that my coins will still be valid. Your coins are fine. If the fork does not go well and there are two competing chains "old coin" and "new coin" they will both be using today's blockchain as a reference as to who owns what and then split from there, so worst case scenario you will have double the coins, one for each fork. |
|
|
|
Alright I got Bitcoin XT up to date and running, 16 active connections... looks and feels exactly the same as QT or Core.  |
|
|
|
My understanding of Gavin's motive is that the hard fork is purely ego driven. There's no urgency to change block size. He just wants to be dramatic and make his personal mark on it. But controversy, technical-wise, is that some Bitcoin users may have their coins lose compatibility with the new implementation. In a sense, it may be Gavin and Hearn's attempt to hijack the Bitcoin name and implement their own coin or make changes to the protocol.
Everything you said is inaccurate. The reason there is a debate is because there are a lot of people on both sides of the blocksize increase, Gavin is not even close to being alone on wanting to increase the limit. He does not want to be the one to make the call on what happens. If you haven't watched a recent Q&A with Gavin and Mike you should, they specifically discuss the blocksize issue at the 27 minute mark https://youtu.be/RIafZXRDH7w?t=27m50sAlso no one is going to lose any coins unless you are a miner receive block rewards and you start mining on the "wrong/old" fork. |
|
|
|
I like the idea that XT progressively increases the blocksize limit, but I think it would be better to fix core instead of switching entirely. However I need more information comparing the two. It would be nice if someone could post a quick comparison table between core and xt so everyone knows what they are voting for.
apparently it has only two new features which are getutxo and double spend relay enhancements. and Core was not the original name also, XT is returning more to the QT path as a name... OK was able to find more info on the github page: https://github.com/bitcoinxt/bitcoinxtBitcoin XT is a patch set on top of Bitcoin Core, with a focus on upgrades to the peer to peer protocol.
1. Relaying of double spends.
2. Support for querying the UTXO set given an outpoint.
Bitcoin XT is more experimental than Bitcoin Core, and has a strong emphasis on supporting the needs of app developers and merchants. By running it you not only provide additional services to the network but help build confidence in the implementations, contributing towards consensus for inclusion in a future version of Bitcoin Core.
XT uses the same data directories as Core so you can easily switch back and forth. |
|
|
|
|
I like the idea that XT progressively increases the blocksize limit, but I think it would be better to fix core instead of switching entirely. However I need more information comparing the two. It would be nice if someone could post a quick comparison table between core and xt so everyone knows what they are voting for.
|
|
|
|
|
Bitcoin will die a quick terrible death.
I feel sorry for all of you therefore I will do you all a favor by purchasing your worthless coins for $20 each.
Better get out quick, much FUD.
|
|
|
|
It is actually bad for bitcoin as it takes away the decentralized part away from bitcoin. And it is hard to trust them as they might sell for fiat for their further investments.
People have a tough time adopting to new concepts that didn't exist before. All they know is they way is has been, and it's difficult to change the way something has been done their entire lives. They try to push it into something they already know, which is what we are seeing here.  |
|
|
|
|
Not much really, 12.5 every 10 minutes is still a lot. ~9 years from now when it drops to around 3 every 10 minutes will have a larger impact on the price, probably enough to push it into the 5 figure range. But honestly who knows, if there's an explosion in demand the price could seriously take off before any of the halvings. It will be interesting to see what happens.
|
|
|
|
|
Just the name alone is not much, I don't believe .am's rank very high in search engines. Still great to have any bitcoin.? domain though. You should add some content and have other websites that link to yours to and you could really increase the value. Put up a block explorer or faucet and start driving some traffic.
|
|
|
|
|
If we can't come to an agreement soon then I will do this and this.
What a terrible and misleading title, he's not quitting or making a threat. Someone needs take a stance on resolving this issue and Gavin has been brainstorming openly with the public and different solutions which I commend. Openly proposing solutions and/or methods to resolve is what we need. If trolls are going to spread FUD on every Gavin post, then so be it; that is what trolls do.
|
|
|
|
However I am optimistic since he is starting a firm that advises on digital currencies, so that means the legislation is at least partially positive and he believes there will be a big enough bitcoin market for his firm to be successful.
It means it's probably going to be so complicated and expensive that you'll need to hire him. Imagine a nice clear pool. Then some crook dumps a ton of shit in it, stirs it up and says he will charge you to help you navigate through it. Sadist thing is that all the VC and bitcoin public figures that were riding the coat tails of the drug market profits see this as another coat tail to ride  . Bastards. He's starting a bitcoin business. It's not a wallet or exchange, but a consulting firm and IMO that is very promising that he believes there is a future in being a bitcoin regulation consultant. That means he expects the currency to have future demand and not die off. I agree what he did is shady, create the rules then profit from it. |
|
|
|
I think you would be better off keeping track of users balances off chain and on a mysql database. Once the user reaches 10,000 satoshis or whatever amount you choose is enough then you have them go to a cashout page and send the payment. Maybe try this one out that uses blockchain.info API https://github.com/zelles/blockchain.info_Bitcoin_Faucet_v.0.1.3Oh yea, and if you do use the above, you will need enable API access in the settings AND white list your servers IP with blockchain.info. |
|
|
|
|
When it didn't happen on Wednesday I pretty much wrote it off as not happening this month. He's a liar and he's going to drag this out as his last legacy before he leaves office. However I am optimistic since he is starting a firm that advises on digital currencies, so that means the legislation is at least partially positive and he believes there will be a big enough bitcoin market for his firm to be successful.
|
|
|
|
|
Time to pick up a new hobby. Watching the bitcoin price has been so boring. No walls, no sell offs, no rallys... looking at the 1 day looks like bitcoin has flatlined and volume is abysmal. I guess everyone is waiting for someone else to make a move.
|
|
|
|
Glad you guys were able to hit your goal! The product is unique and looks quite promising. Be sure to keep us early-birds posted on updates as they're available  |
|
|
|
How does it go into the abyss? Are you able to track the payment on the blockchain or is this all off chain transactions with xapo? Looking at their API doc: https://developers.xapo.com/api/mpayment/They use a Receiver ID <dt>receiver_user_UID</dt>
<dd><code>string</code> <p>an ID used by your app to uniquely identify the receiver.</p></dd> This is your payment code on that faucet: function pay($to, $amount, $comment)
{
$settings = $GLOBALS["settings"];
$serviceUrl = "https://api.xapo.com/v1";
$creditAPI = new XapoCreditAPI($serviceUrl, $settings['xapo_app_id'], $settings['xapo_secret_key']);
$currency = "SAT"; // SAT | BTC
$unique_request_id = uniqid();
return $creditAPI->credit($to, $currency, $unique_request_id, $amount, $comments);
} I've never used xapo but if that receiver ID is what they are using instead of BTC addresses, that would explain why it only works with xapo accounts. |
|
|
|
|
Show Posts
