3 ms·
Having gone through the pain of writing code like this in the past, this looks amazing. How are you planning to charge for decimals? In your code sample, you u
by zomglings 6y ago
Having gone through the pain of writing code like this in the past, this looks amazing. How are you planning to charge for decimals?
In your code sample, you use from: 'Alice' but list transactions for some kind of complicated balance ID. Where did that ID come from?
- zomglings 6y agoAlso, your RunKit sample is not working since they don't have the decimals package available (assuming it's published on npm already).
- andriosr 6y agoI'll add a note to the post, thanks! Working on that now.
- andriosr 6y agoGreat question, each Account holds a list of balances, one for each currency. When you first use a given currency on an Account, a Balance is created along with its id. The ID comes from the list of balances of the Alice Account.
- zomglings 6y agoIs there a way to access that balance ID programatically? Right now, it is a magic string and it isn't clear to me how I would get access to it in my program. Perhaps from a return value on decimals.transactions.create? Also, shouldn't decimals.transactions.create be asynchronous?
- andriosr 6y agoPricing is similar to the Segment.io model, you pay for the number of accounts, in chunks of 10k. You get the most value when you do more transactions, so that's why we don't charge for that, we don't want companies limiting what they to with Decimals to save money. Also important to note is that this is not one more layer in the payment cake taking a percentage of your revenue, the pricing is based on API usage, with no relation to your revenue.