Nice update, with some help from bit_exo, the house edge is now fixed.

1% on first tile you click.
Then, 0.50% on the other tiles you click. (on a same game)

Most faucet traffic is from Russia and Ukraine. Good idea to block boths.

you can not join us , the reason is above.
sorry for that.

There is no simple way to get the "sending address"[1]. You have to check the inputs, but more often than not there will be several inputs. Its better to let the user set an address you store in your database along with their other information.


within decoded_tx you will find a "vin" section with a value "vout" and a txid. If you check each of the txids you will see that they have a "vout" section. The outputs that created the inputs that are used in the TX you received. Find the one where "vout" matches "n" and look up its address. In this example there are 4 inputs, all "from" the address "1NgrpJJj2PMj9RsHutVK7vf8dchcpfM4YZ", but you need to decide how you want to handle different addresses.

IIRC the data is mixed formatted, arrays within JSON, but that might be different for PHP.

[1] there is no such thing

 You mean listing your addresses that've received payment(in the past)? Yep that's possible as well. Run this command->. Basically, it lists only addresses that already 've received transactions. However, you can list all the addresses by setting the first argument to 0, and the second one to true->

Run this command-> . This'll return the current bitcoin address for receiving payments to this account. If <account> does not exist, it will be created along with an associated new address that'll be returned.
P.S.-> "getaccountaddress" will return the same address until coins are received on that address; once coins have been received, it will generate and return a new address.

Then it's your problem. You should know that there are some risks when buying account.

Ahh... That's why I vaguely familiar with your username, we had once post on the same board. Here, let me show you a link of your post to refresh the memory.


And again,


Hmm... Just like another user who said that star-censored word about secondstrade but then turns out applying on the very sig campaign.
And just like before, Admin, the decision is yours, but for me myself, I won't hire someone who talk bad about my company. I believe it won't show a good image if my "employee" is bad mouthing about my company and... not recommending people to invest on it.

-walletnotify will run twice per transaction, when it's first seen on the network as unconfirmed, and when it gets it's first confirmation.

To track more than one confirmation you need to use -blocknotify

-walletnotify will run twice per transaction, when it's first seen on the network as unconfirmed, and when it gets it's first confirmation.

To track more than one confirmation you need to use -blocknotify

   -alertnotify=<cmd>    Execute command when a relevant alert is received or we see a really long fork (%s in cmd is replaced by message)
   -blocknotify=<cmd>    Execute command when the best block changes (%s in cmd is replaced by block hash)
    -walletnotify=<cmd>    Execute command when a wallet transaction changes (%s in cmd is replaced by TxID)


So for individual transactions, you would want to use walletnotify, eg:


Then in script.php, you could do something like:

of course with sanitization, error checks, etc....   ;-)


If you are likely to have more than one tx in a given block, a more efficient way to do it can be to include the block-hash with the tx in the db, so you can look up all tx by block.  Then use blocknotify instead of walletnotify.


edit:  and don't forget that the txid can change due to transaction malleability.