Co-founded Netribution.co.uk to help indie filmmakers in 1999. Co-writer of the Film Finance Handbook (fundyourfilm.com), web designer for non-profits, CiviCRM community member & occasional filmmaker.
That's very interesting – thank you. Did you get the sense that the Uphold API team would update their docs, or can you document your processes? Or do we each need to communicate with them directly to learn how to get Payment Pointers / ILP working with their API?
Interested also to hear to you chose ODRL. I have been looking at Accord wrt machine+human/Ricardian contracts; and while there's lots interesting there in making contracts execute code; it seems to miss that strength of a semantic framework, such as RDFa in CCRel.
Thanks for your reply, Nic! So far, the uphold team seemed very responsive and helpful. The part that's missing from the docs right now boils down to this:
You can generate an ILP pointer for a card by calling the POST /me/cards/:card/addresses endpoint (described here) and passing the body:
{ "network": "interledger" }
Note that you can currently only generate 1 payment pointer per Uphold card.
Co-founded Netribution.co.uk to help indie filmmakers in 1999. Co-writer of the Film Finance Handbook (fundyourfilm.com), web designer for non-profits, CiviCRM community member & occasional filmmaker.
Just a heads up: I've got some bad news about Interledger support in Uphold. Turns out it's currently receiving only, not sending. So we'll have to find a different way of doing payments.
Co-founded Netribution.co.uk to help indie filmmakers in 1999. Co-writer of the Film Finance Handbook (fundyourfilm.com), web designer for non-profits, CiviCRM community member & occasional filmmaker.
That is bad news - thanks for the update. I guess we have to wait for Rafiki? write.as/coil/introducing-rafiki-a.... Tho "we will spend most of this year on the implementation" sounds like it could be a bit of a wait.
This is exactly what Rafiki is looking to fix, and yes won't be immediate but its an open project and will have incremental releases. It should be worth the wait considering how many of these issues are now bottlenecked. Our collective work in Web Monetization has help drive these updates to the ILP. We are discussion it as a community here: community.interledger.org/grantfor...
For further actions, you may consider blocking this person and/or reporting abuse
That's very interesting – thank you. Did you get the sense that the Uphold API team would update their docs, or can you document your processes? Or do we each need to communicate with them directly to learn how to get Payment Pointers / ILP working with their API?
Interested also to hear to you chose ODRL. I have been looking at Accord wrt machine+human/Ricardian contracts; and while there's lots interesting there in making contracts execute code; it seems to miss that strength of a semantic framework, such as RDFa in CCRel.
Thanks for your reply, Nic! So far, the uphold team seemed very responsive and helpful. The part that's missing from the docs right now boils down to this:
Thanks alot Joep, that's great to know, especially as it appears straightforward enough to add cards.
Just a heads up: I've got some bad news about Interledger support in Uphold. Turns out it's currently receiving only, not sending. So we'll have to find a different way of doing payments.
That is bad news - thanks for the update. I guess we have to wait for Rafiki? write.as/coil/introducing-rafiki-a.... Tho "we will spend most of this year on the implementation" sounds like it could be a bit of a wait.
This is exactly what Rafiki is looking to fix, and yes won't be immediate but its an open project and will have incremental releases. It should be worth the wait considering how many of these issues are now bottlenecked. Our collective work in Web Monetization has help drive these updates to the ILP. We are discussion it as a community here: community.interledger.org/grantfor...