You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think what we need is a receipt verification function.
input: the target BTC address, amount of BTC received at the target BTC address, number of confirmations
output: true if the amount of BTC has been received at the target BTC address with the specified number of confirmations; false otherwise.
a subroutine is also needed:
input: BTC tx hash
output: how deep is the tx embedded in the main branch? of course, the returned value reflects the "current" status. for a current ETH block height, there is a corresponding BTC block height.
any comment? can we have such a function?
and there is an ultimate question: why do we trust the function? is it trustworthy?
The text was updated successfully, but these errors were encountered:
jackzhp
changed the title
a function
receipt verification function
Sep 11, 2020
While Ethereum is primarily focused on its native cryptocurrency Ether (ETH), it is possible to interact with other blockchain networks, such as Bitcoin (BTC), through various mechanisms like smart contracts or oracles. However, it's important to note that Ethereum does not natively support Bitcoin transactions or provide direct access to Bitcoin's blockchain.
To achieve the functionality you described, you would need to rely on external services or oracles that bridge the Ethereum and Bitcoin networks. These services can provide the necessary data and verification mechanisms to confirm BTC transactions and their confirmations.
Regarding the trustworthiness of such a function, it ultimately depends on the implementation and the reputation of the service or oracle providing it. It's crucial to thoroughly research and vet the service or oracle you plan to use to ensure its reliability and security. Additionally, it's always a good practice to review the code and seek third-party audits if available.
Remember, when interacting with external networks or relying on third-party services, it's important to consider the potential risks and trade-offs involved.
I think what we need is a receipt verification function.
input: the target BTC address, amount of BTC received at the target BTC address, number of confirmations
output: true if the amount of BTC has been received at the target BTC address with the specified number of confirmations; false otherwise.
a subroutine is also needed:
input: BTC tx hash
output: how deep is the tx embedded in the main branch? of course, the returned value reflects the "current" status. for a current ETH block height, there is a corresponding BTC block height.
any comment? can we have such a function?
and there is an ultimate question: why do we trust the function? is it trustworthy?
The text was updated successfully, but these errors were encountered: