Interoperability between communities and platforms with Credit Commons protocol

General
1

I’d like to open a discussion about interoperability between different community currency / platforms using the Credit Commons Protocol (CC).

Right now, most exchange communities run as isolated instances, members of one community can’t easily exchange with members of another, even when both run same software (TimeOverflow.org is multi-tenant but every organzation (community) is isolated ). Credit Commons offers a federated model (a tree of “trunk / branch / twig / leaf” nodes, no shared central database, cryptographic hash-chain integrity between nodes) that seems like a good fit for connecting independent communities without forcing them into a single centralized platform.

From TimeOverflow (ADBdT.org) We’ve opened a concrete implementation proposal in the TimeOverflow repo, outlining how we’d add Credit Commons support (data model, API endpoints, transaction lifecycle, phased rollout starting with bilateral exchange between two instances):

:backhand_index_pointing_right: Federation via Credit Commons Protocol: Cross-Bank Time Exchange · Issue #846 · coopdevs/timeoverflow · GitHub

Our first priority is enabling exchanges between users from different communities within the same TimeOverflow instance, and as a next step, connecting a TimeOverflow organization with external ones — whether another TimeOverflow instance or any other CC-compatible platform.

Looking for collaboration and funding

ADBdT is exploring grant opportunities to work on this topic together with CEN. If your organization is interested in interoperability or would like to explore funding this work jointly, we’d love to hear from you :blush:

1 Like
2

Sergei, what you need is a single credit commons instance to serve the time overflow network, and you can use the reference implementation.

The tricky part is coding a new transaction form and transaction type into timeoverflow.
You can implement a restricted feature set to make it less complicated, for example not supporting pending transactions, or assuming a particular workflow.

To help with the platform, a number of functions and objects are already available in the repo cc-php-lib. So it shouldn’t take a developer more than a week or two. If timeoverflow is in php, I might be the best person to do the job, although Esteve is pretty familiar with the API as well.

3

Great @matslats !! TimeOverflow it’s Ruby on Rails

Also I share here the conversation on github related to this topic Federation Options for CES2: Inter-Exchange Transaction Architecture · community-exchange-network/komunitin · Discussion #919 · GitHub