RADR has its unique issuance algorithm, which is one of the reasons why few third-party exchanges access VBC transactions. The third-party’s user assets are not on the RADR main chain but are managed by internal bookkeeping(according to the exchange’s support for digital assets such as XRP and EOS, the user balance only exists in the custodian account of the exchange). Therefore, the third-party’s internal user assets cannot participate in the issuance calculation on the RADR main chain and no user will be willing to make VBC transactions in a third-party platform.
Now, RADR rolls out a set of third-party issuance interfaces, supporting issuance income calculations of the third-party institutions and exchanges. With the specific issuance interfaces, the third-party can activate it to build a one-to-one correspondence between the third-party internal accounts and RADR main chain accounts. So even if user assets exist in the third-party, they can still be accumulated to the corresponding main chain account balance, participating in the general issuance calculations and easing user worries about trading VBC on the third-party platform.
It enables more third-party platforms to access VBC transactions, enriching the RADR ecosystem, and enhancing the decentralization. For the specific interface implementations, developers can access the Developer Centre Wiki ( https://wiki.radarlab.org/third-party-access ).