Old daemon and wallet version 0.18.3
Question or two for the more informed
j_scheibel last edited by j_scheibel
Hey everyone, I was thinking about putting up a feathercoin (only) e-commerce site. I may not, the debate is real :)
I was curious about somethings I think might be useful (but might be overkill too).
Is it a terrible idea to make a wallet that can verify the receivers identification. I was thinking that maybe the wallet could go out and check a website for the intended recipient. Ex: amazon wants 100 FTC payment they provide a wallet address in the url qc code. The same code links to their website via ssl and validates said payment address is theirs.
It could all be done via https and a standard made up by whoever. No change to anything in the coin.
But another thing comes out of this , is there a way to make it so a receiving address can only be used once and only for an exact amount? Why? To prevent transaction errors.
I was basically trying to figure out ways to build confidence for the user buying that: 1 their transaction is going to the right place and 2 they pay correctly.
these are all extras but it’s a case of having the strongest audit trail possible. It would even be nice if the https auth key (the signed one) ended up in the block chain but I don’t know if messages have room (probably) and requiring the comment is again probably a wallet thing.
I think there are solutions available already.
Let me check.
I know, that @ChekaZ has mentioned a solution to integrate FTC payment to a web shop.
It didn’t sound that complicated ;)
@j_scheibel BTCPay which now supports FTC should solve all of this for you.
It can also run in a docker container for easy portability
j_scheibel last edited by
@acidd i’ll check it out.
@AcidD Is a special BTCPay version for Feathercoin required, or will the ‘standard’ BTCPay sufficient?
Sounds easy :smile: