Agreed on Tron.
I am just going to structure subscriptions on approve alone, and listen for approvals on a node backend to update the billing contract. (…)
(…) Since they are approving only a contract address to move their tokens, they have the same security as using an approveandcall function.
billingId is a random int (as the documentation says, both sides agree on it off-chain, e.g. it is generated by the server and sent to the client). Once you tight-pack the
data argument correctly, everything should go smoothly…
Here’s our function that encodes stuff (really “drafty” implementation :) ):
Oh Woody, let’s try to break your critique down :)
Using approveAndCall(), can I pass all of the relevant parameters required for allowRecurringBilling()? Do I have to use the function specifically from your token contract to get this to work?
Try checking this thing:
2.4.2. If the customer hasn’t approved at least `value` tokens for a smart contract, `allowRecurringBilling` errors.
(find this in a big comment explaining how the contract works)
I am really happy that you are trying to get this to work, as well as in general, feeling happy about people starting to implement real things on top of blockchain.
Did you try our Recurring Billing smart contract factory? This is a super easy way to get started; I tried to explain the…
Hi Josh! Thank you for your feedback!
As of now, Trickle provides an engine for hourly-based agreements. Everything else like milestones you’ve suggested is something that two parties can easily agree “offchain”. For example, having a long-term agreement, they can get in touch each week and decide whether or not to go…
Hello! Thanks for the feedback!
Indeed, it can be, and there is a little we can do to deal with this problem in terms of programming. Normally, when two parties agree, they should have at least some conversation and a basic validation of each other, which lowers the risk. But anyway, using Trickle is the least risky option…
Hello Lundrim! Thanks for your feedback!
Simply put, there’s no need in central back end server as far as you have a simple app. Surely you can put all the data to IPFS (but ensure you know how to maintain it).
But you’ll start having issues with performance once your app has at least a couple of…
Hello Hugh! Thanks for your feedback!
To answer your question, take DApps that use a custom back end additionally to what you can get from an Ethereum node (or nodes pool like Infura). This is required in a couple of cases:
Thank you, John. I really appreciate your feedback!
Indeed, Tron is quite trendy today. Once more and more crypto exchanges start to support Tron tokens it can get close to Ethereum. While Ethereum also gives great hopes with its upcoming updates.