Peter Li
Subscribe to our newsletter to stay up to date on the latest developer news, tools, and articles.
Join Our Ecosystem
Additional Customized Feeds
Receive additional filtered content based on your liked content. Save time finding relevant material and enhance your development experience.
Training Courses
Access multiple Corda development training courses including CorDapp, Network, System Admin tracks. All available in your customized dashboard.
Don’t have an account?
Sign In
Don’t have an account?Lost Password?
Enter your email address to receive instructions on how to reset your password.
We sent you an email with a link to finish resetting your password.
Can’t find the email? Try checking your spam folder. If you still can’t log in, have us resend the email or contact us.
Forum chevron_right Peter Li
Hi Igor,
Corda 5 has not enabled the attachment functionalities yet. But it is on the roadmap for features. We will most likely send out a newsletter when new features are added to Corda 5.
Please stay tuned.
-Peter | R3
Hi Munera,
Corda 5 has token capabilities by default. The TokenSDK is built into the core of Corda 5. You dont need to add the SDK anymore.
-Peter | R3
Hi Ryan,
This seem like an open-ended question. You can of course build an IOS app on top of your corda solution. Corda is backend distributed ledger platform where it stores data decentralizely, conbatting the distrust that happen when data at rest.
You can choose to develope it on our legendary Corda 4 or the newly released Corda 5. On Corda 4, you do need to implement a REST client to connect Corda and your app. Whereas on Corda 5, the Corda flow triggering are exposed via swagger APIs, so you can directly connect Corda with your IOS app.
More info can be found at here. Happy developing!
-Peter | R3
Hi Yuyou,
We had replied your email. Please feel free to reach out again if you have further queries.
– Peter | R3
Here’s a quick generated js client in React we put together. https://github.com/amoothart/currency-mbs-ui/tree/master/src/services
This code works but is only suitable for demos/PoCs because it is polling the Corda cluster.
– Austin, R3
I think you slightly misunderstood the concept of Corda 5. Corda 5 has vNodes that can be run on the same cluster (e.g. provided by a SaaS provider) – but that is not required.
A Corda 5 network can span many clusters run by different operators, and there is nothing stopping participants running their own clusters and owning the full stack.
-R3 Christian Sailer
Hi Philip,
We had identified the bug and will work on it. We had opened the ticket [CORE-15098] to document this bug.
Hi Kiran,
https://developer.r3.com/next-gen-corda/
You can download all the files you need to build a Corda 5 environment at the above link.
The Contract testing API and flow testing API will be released soon.
Hi both,
The latest version of the Corda 5 beta is Iguana (this is the 4th version of the beta). download link is here: https://developer.r3.com/next-gen-corda/
With Iguana, you would need both digicert-ca.pem
and gradle-plugin-default-key.pem
to sign the CPI. This includes the mgm cpi, the notary cpi, and the App cpi.
Corda 5 will be available in 2023 Summer. We had already published a public release of our beta 4 release of the Corda 5 software.
Here is the link: https://developer.r3.com/next-gen-corda/
The reason is quite simple. It is to avoids duplication of code, which is easier to debug. And more that there’s no need to write it twice as the responder logic is identical in both.
That is, for flows that share the similar responder logic, they all should try to have the finalization code in a seperate file and keep re-use it.
Here is what happen if the transaction proposer does not add his/her own signature via the addSignatories() function:
You will get an error saying: The publickeys do not have any private counterparts available
Subscribe to our newsletter to stay up to date on the latest developer news, tools, and articles.
Cookie | Duration | Description |
---|---|---|
cookielawinfo-checbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
cookielawinfo-checbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
cookielawinfo-checbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. |
cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". |
viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |