Client-side computation of party onboarding transactions and hash

Open
#17 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
java, typescript
Domain
backend-api-design, distributed-systems

Research direction

Start with the referenced party-allocation-service.ts lines 111-134 and compare that implementation with the Java JSON API bindings repository. Work through the three checklist items—client-side topology transaction hashing, combination, and generation—and consider the issue done when all three are implemented client side.

Written by the indexing model from the issue text.

Description

Motivation

Remove the need to trust a participant node and validator app to prepare the right topology transaction

Background

The kind of code to port is this one: https://github.com/hyperledger-labs/splice-wallet-kernel/blob/8d05dd8e30e4b9e8545aa5db8bf11fa546ca9794/clients/remote/src/ledger/party-allocation-service.ts#L111-L134

Steps to get there
  • implement topology tx hashing client side
  • implement topology tx combination client side
  • implement topology tx generation client side
Dominant language
Java
Stars
1
Forks
0
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from digital-asset/ex-java-json-api-bindings

All issues in digital-asset/ex-java-json-api-bindings

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.