Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Register Indentity command #13

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from
Draft

Conversation

pshenmic
Copy link
Owner

Issue

We need a way to register an identity in the application. It is done via providing a private key from the address with the DASH balance, which will be used to register an identity in Dash Platform and fund initial credit balance.

The command crafts and broadcast signed AssetLock transaction in the Core network, and then uses the InstantLock (ChainLock) proof to create a IdentityCreateStateTransition in the Dash Platform network.

Operation involves creating transactions in two network (Core, Platform)

Things done

  • Serialize & Sign Core AssetLock transaction

@pshenmic pshenmic added the enhancement New feature or request label Oct 31, 2024
@pshenmic pshenmic self-assigned this Oct 31, 2024
@pshenmic pshenmic marked this pull request as draft October 31, 2024 10:00
@pshenmic
Copy link
Owner Author

pshenmic commented Nov 12, 2024

It is not possible to achieve that at this time, because InstantLock / ChainLock data that is needed to create IdentityCreateTransition in Platform only available from the Core ZMQ interface, and it basically blocks implementation, because platform-cli relies on DAPI endpoint.

There is a support of InstantLock messages in the DAPI via subscribeToTransactionWithProofs query, but it work through BloomFilter, which does not have an implementation in the rust-dashcore and thus we can't use that method.

Other indexing services like Insight API, or rpc.digitalcash.dev, also does not provide that information, because Core itself does not have such data in the RPC

The best scenario, if Core could implement instant lock \ chainlock buffer data in one of the RPCs, so we could easily fetch that via HTTP gateways.

Another approach would be to implement a separate, hosted service, that will allow you to subscribe on transactions and return you instantlock data that has access to Core ZMQ, but this gotta be done as a separate project (f.e. https://github.com/maxmanukian/dash-websocket)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant