pull down to refresh

0 sats \ 1 reply \ @AG 13 Nov \ on: Branta's Approach To Bitcoin Payment Address Verification: Triangulated Security AGORA
This is interesting, thank you for sharing.
So how merchants can benefit from BRANTA? Do you have any guide on how to set it up in BTCPay, Zaprite, and others or a developer is needed for the implementation?
Businesses using Guardrail automatically send the encrypted address to the Branta API (which expires after TTL seconds)
Why should a business put a tag with their business name on (tinting?) each generated address? Isn't this like auto AMLing somehow?
Does verification for on-chain addresses, mean you do NOT keep any data received via API? or it's stored somehow somewhere? And even if so, how do you possibly know if a vendor is authentic or an imposer?
write
preview
0 sats \ 0 replies \ @keith_gardner 13 Nov
Hello! I'm the founder.
Here are docs for BTCPay: https://developer.branta.pro/guardrail-tech/btcpayserver-plugin-setup
We need to make Zaprite docs. It's a no-code Connection within Zaprite; turn it on, drop in an API key.
Developers are needed for custom integration, but its pretty straightforward.
Re AML; With ZK, Only sender/receiver know the receiving and sending address, Branta doesn't. Branta is not queryable in the sense that other parties can do lookups.
Answer below on Imposters
reply