Topic: Bitcoin wallet need this function - Payment Callback - page 2. (Read 513 times)

I don't know the correct programming term, but its clearly stated OP needs a 'callback' function for maybe OP e-commerce site to verify the confirmation of the Bitcoin, and make the product ready to be shipped.

---

OP Why wouldn't you use a crypto payments processor? I believe it could save you a lot of time, coingate, coinpayments are a few examples.

i think what the topic creator is asking is about full bitcoin nodes/spv which interact with ntwork nodes (random connections)

things like electrum and other lite wallets rely on more specified/listed servers as a dependant parent (third party)
thus as the topic creator said not relying on third party so suggesting electrum is not the solution to the topic creators issue.

the thing the topic creator is also hinting is that he cant see if his recent transaction is confirmed independently (using a full node/spv) untill the blockchain is fully downloaded. (stored full node / then pruned spv)
...

the topic creator then uses an example of having full node peers giving status updates of particular transactions using an example that resembles that of what lite wallets and webserver api's do. i feel the topic creator is just saying there needs to be a way to see confirmed balance without having too wait for the full sync when using a full node or SPV AND not having to rely on specific server/third parties

i did approach the topics scenario firstly with the mindset that the solution is to simply get a node to bloomfilter particular addresses for updated info from random peers.
pro: independence from specific 3rd party as request can be made to any relay network node
con: the user needs to regularly spam request its random peers to get update info

i also approached the topics scenario with the mindset that getting random peers to temporarily monitor said bloomfiltered addresses for a short period (1 hour-1day) and then the peers specially announce when certain known tx's appear.
pro: independence from specific 3rd party server
con: temporary dependant on certain peer for a temporary period
con: adds extra 'parenting' services to peers who are the 'temporary monitor'.
con: peers get to know certain addresses other peers are interested in (the privacy concern of bloom filtering being abused in such a way)

the way i see a solution would be to have a UTXO set milestoned periodically and also have beside it a updating utxo set that shows the relevant changes since the milestone.

this way a node can get updated info from the random relay network, without having to download the entire blockchain. and without having to hand specific peers a list of specific addresses to monitor

that way without having to download the full blockchain first. without having to list specific addresses, network peers can request updated info on confirmed transactions from network peers independently via the main relay network

Third-party services can integrate such function on their own systems if they so do like. Personally, I find this as a useful tool since I'll be notified on the get-go whenever someone pays me, though I don't find it necessary for wallets to do this. AFAIK electrum does this everytime I am receiving something, and has never failed not even a single time to notify me that I have something coming in.

The actual Bitcoin protocol and the Blockchain should never have a function like that, because once a bitcoin transaction is done, it should never be reversible for obvious reasons.    Yes, third party services that are built on top of Bitcoin can have that function, because they can use their own internal database and these database transactions can be delayed or cancelled without affecting the actual Blockchain.  

Bitcoin was built for people not to rely on third party services, so this is also not the ideal solution.  

Unfortunately, I don't know the code because I don't learn about programming. But I only know that when I don't want to wait for a long time, I only need to use a high fee to get a fast confirming in the transaction and so far, it runs smoothly for me, and I don't have any problem to pay in a fast time.
I think the time consuming for the transaction will be back to the fee that we used, and I think we could use the higher fee, so we don't need to wait for a long time like what I did. But it's up to you because you are the person who makes every transaction

Merchants needs to work on the accepting bitcoin with the perfect gateway which can move the transaction smoother than the regular transaction takes time of payment and pending transactions.
We need to work on lighting network and segwit payment method for faster transaction for the people wishes to have bitcoin acceptance merchant deals.

I think no one merchant will agree on this proposal. This will be a big disadvantage from every merchant because the service or fhe product will the merchat will be ruin when the transaction will return or refunded. So I think bitcoin industry will not develop this kind of function.

Is callback is the correct term to use here? It literally means that a peraon can callback the transaction, similar to the chargeback facility that Paypal uses! Am I missing something here?

Or are you referring to an information functionality that tells you how much bitcoin someone sent to your wallet just after initiating it?

If the seond one is your concern, start using greenwallet. It comes with this functionality for both incoming and outgoing transactions.

I also understand your point, to check the current state of the transactions is necessary to take a look at the wallet.

I'm not particularly sure if any wallet got that function and i will definitely check later and write here depending on if i find something. I don't think that Bitcoin developers themselves should implement something like that for now and maybe just maybe it is only necessary for wallets to do so.

A lot of people will see it as something not really important or redundant.

I believe bitcoin already have the necessary functions that is needed and suggesting a call back function is an unnecessary demands on the developers. But call back function if established and in such that one can cancel unconfirmed transactions and found returned back to the originating wallet will be better and that will help merchant on there in store transactions.

http://docs.electrum.org/en/latest/protocol.html

Electrum server uses blockchain.address.subscribe to start listening to transactions for an address, and if any are found in a new block, it sends notification to the client. And client somehow reacts to these notifications to then send a system notification and update the ui, I'm sure you can hook into it if you try harder.

Edit: I don't even know Python, but I'm sure that this is close to what you are looking for: https://github.com/spesmilo/electrum/blob/9b4e490e3cffe07c0f5a5e373b0834c6915baac1/electrum/gui/qt/main_window.py#L651

I clicked on this thread expecting details on exactly what @Beerwizzard assumed: that you propose some sort of chargeback.
But unlike him, I've read your post and understood your point (although, as others said, you may not actually need it)
However, maybe my English is not great, or maybe your topic title is misleading for the ones reading only the title. 

I don't get your posts, callback function is just to let your system know that this particular order is confirmed paid and ready to be shipped, nothing to do with chargeback at all. Unless you want to be awake 24hr staring at the bitcoin wallet to check incoming payment then its different story.

If such function would be implemented without any 3rd party it would be even worse than current PayPal / Bank chargebacks. In case with a chargeback via bank you still have to submit a chargeback request that would be reviewed by a special team that would refuse to make a chargeback if they find that that was not a fraudulent transaction.
If every single person would be able to make a chargeback via his wallet then it would probably open big opportunities for scammers.

I don't think it needs to be done, the available system is better than what you want and you imagine.
once again I explained that bitcoin does not need that.

I have read electrum/electrum merchant doc, their wallet don't have the required functions like callback upon detecting transactions/confirming transactions atleast without using any cronjob. If any paypal/mastercard service need to use cronjob to accept payment I would gladly listen to it.

Do you think developers are that stupid and have never though about something like this? Well, my electrum wallet sends me system notification whenever my wallet receives a transaction, and this was the case for a long time. Read the documentations for bitcoin libraries and google before coming here complaining how Bitcoin needs some functions, as if it doesn't have them yet. Plus there are third-party services that watch addresses and send notifications, though I doubt that they are suitable for programming at scale.

Accepting bitcoin as a merchant is never been that smooth other than its highly volatile prices and slow confirmation (1mb block size really?). Now try accepting bitcoin payment for customer to purchase your product/services is another big issue as well.

Bitcoin wallet (especially light wallet) need to have a proper callback function without downloading the whole pain in the ass 150 GB blockchain file into our VPS/server or relying on some 3rd party API like blockchain.info. Paypal/Mastercard/Visa has much better callback system than bitcoin system.

Do you support a light wallet to have callback function that will automatically call to your server whenever a payment is received, how much received, tx id, confirmation status using programming script in JSON format that works with Java/PHP?

Automatic Payment Callback JSON

Automatic callback function to your serverside script (http://127.0.0.1/myscript) without the need of cronjob or manually curl the wallet. So that your computer will automatically detect transaction and mark paid invoices.

Xpub Generate Payment Address (Exists in electrum merchant)
{
   "address": "38H49jK1uvm8dLgykM8LM2nSBN1eK24wj9",
   "index": 0
}

Unconfirmed TX
{
   "address": "38H49jK1uvm8dLgykM8LM2nSBN1eK24wj9",
   "amount": 2000000,
   "txid" : "56d1cc5ec0a531b783680d880fd4b0a6bb62242162c1ead252bf2fc29c14e9d5",
   "status": "0"
}

Partially confirmed TX (1~2 confirmations)
{
   "address": "38H49jK1uvm8dLgykM8LM2nSBN1eK24wj9",
   "amount": 2000000,
   "txid" : "56d1cc5ec0a531b783680d880fd4b0a6bb62242162c1ead252bf2fc29c14e9d5",
   "status": "1"
}

Confirmed TX (>3 confirmations)
{
   "address": "38H49jK1uvm8dLgykM8LM2nSBN1eK24wj9",
   "amount": 2000000,
   "txid" : "56d1cc5ec0a531b783680d880fd4b0a6bb62242162c1ead252bf2fc29c14e9d5",
   "status": "2"
}

Related Article :

https://developer.coingate.com/docs/payment-callback

https://www.blockchain.com/api/api_receive

https://www.blockonomics.co/views/api.html


Pardon for my noobie programming skills, Im not from CS major