Prism Node 1.3.1

• Enhance logging messages in repositories and services
• Create output for ProtocolUpdateVersionOperation
• Remove all slf4j usages

PRISM Node 1.3.0

• Remove FlushOperationsBuffer RPC method
• Allow propagating a custom header from the Node settings to the Cardano Wallet
• Fix bug about revokedOn and addedOn equality
• Node CLI was added
• CreateDid, UpdateDid, IssueCredentialBatch, RevokeCredentials RPC calls were eliminated. Use scheduleOperations for sending operations to the Node instead.
• Deprecated logSQLErrors method was removed
• Better trace id support
• Update to cats effect 3
• Remove all usages of AWS S3, removed dependencies on Monix, bitcoin-lib, braintree libraries
• Remove AtalaBlock version
• Update ApiClient sttp version

PRISM Node 1.2.0

This release introduces PRISM Node service, which is published as Docker Image prism-node:1.2.0
Node service receives operations via gRPC requests, publishes them to the Cardano Ledger using HTTP requests to the cardano-wallet, and applies these operations after the corresponding transactions are approved in accordance with PRISM protocol.

Operations supported by PRISM Node

• Create a new DID document
• Update DID by adding and removing some public keys
• Issue new credentials and publish the corresponding proof on the ledger
• Revoke already published credentials

Auxiliary available gRPC calls

• health check to see if Node service is available
• get Did Document to look at the current DID document by its identifier
• get credential revocation time for retrieving information about credential revocations
• get operation info to check the current status of the operation
• get info about the current Node build
• get the timestamp of the latest synced Cardano block

Known issues and limitations

• To preserve the order of operations users need to wait until the status of an operation is CONFIRMED_AND_APPLIED or CONFIRMED_AND_REJECTED. If someone sends two operations sequentially without waiting, then operations might be applied in the reverse order. The probability of this is very low, but it could happen in some scenarios. In most of the cases it’s rather a feature than an issue, e.g. if we need to issue a lot of credentials, we don’t care in what order they should be issued.
• The PRISM Node itself does not provide a way to limit operation submissions. This is normally handled by higher layers in the architecture.
• There is a throughput limit on the amount of PRISM operations the system will not exceed. Given that operations are posted on-chain, the operations throughput is today limited to the underlying blockchain TPS. Given that PRISM events are not validated by ledger rules, this can be scaled by moving towards a layer 2 approach (i.e. batching events/operations off-chain and only posting commitments on-chain). For initial use cases, the current on-chain implementation is simpler and seems to provide enough throughput.

Note for the PRISM Pioneers Program (PPP)

Since this release is mostly meant for the PPP, and in relation to the above comment on operation submission limit, it is worth noting that for PPP we are deploying a node instance for pioneers to play with. If pioneers submit thousands of operations to the node, the operations queue will grow, and operations will have long waiting times to be confirmed

Deployment for summit

this release includes only the content of prism-interactive-demo-web repository, it should be deployed manually following these steps:

1. cd to prism-interactive-demo-web folder
2. build for prod via yarn build
3. build a docker image via docker build -f $PWD/Dockerfile -t 895947072537.dkr.ecr.us-east-2.amazonaws.com/landing:<some tag> $PWD/
4. Log into docker via aws ecr get-login-password --region us-east-2 | docker login --username AWS --password-stdin 895947072537.dkr.ecr.us-east-2.amazonaws.com (you need to setup aws cli for that first.
5. push image to ECR via docker push 895947072537.dkr.ecr.us-east-2.amazonaws.com/landing:test-for-intdemo.<some tag>
6. Once the image has been pushed, apply it to https://atalaprism.io/ in aws console.

BE (connector) of interactive demo flow is not compatible with deployed frontend and mobile apps on play store at the time of creating this tag, because of that there was a need to deploy landing page frontend without deploying the backend.