Soranet 1.0.0

SORANET-1.0.0

Pre-release: 0.4.3-snapshot

Rework hash in listeners (#596)
Feature/expansion remove logic (#587)
Fixed Genesis block (#595)
Added amin permissions (#594)
Updated genesis block (#593)
Only null check for pubkey (#592)
Making createTesterAccount() public (#591)

Pre-release: 0.4.2-snapshot

• Fixed domain priority (#588)
• add expansion details (#584)
• GetAccountDetails by key (#586)
• rework IrohaCredential (#585)

Pre-release 0.4.1-snapshot

• Made registration domain dependent (#581)
• Remove d3TestReportPlugin (#580)
• Updating notary-commons dependency (#579)
• Added a way to register without brvs (#578)
• Test report plugin integration (#567)
• Health check endpoint (#577)
• Merge pull request #576 from d3ledger/feature/d3-944-billing
• Feature/push bootstrap docker image (#570)
• fix negative peer (#574)
  Update eth lib version (#575)
• Fixed shadowjar (#572)
• Notary expansion service (#571)
• fix Jenkinsfile (#569)
• Possible to omit default values of chain listener in Java (#568)
• set BRVS validation time to 10 sec in dev docker-compose (#565)

Release 0.4.0-snapshot

Move bitcoin and ethereum parts to separate repositories.
update License
update Jenkins pipeline
fixing
etc

Decentralized Digital Depository v0.3.0-alpha

• Update Iroha to RC4
• Introduce BRVS

Decentralized Digital Depository v0.2.1-alpha

Distributed Digital Depository is a service platform for decentralized safekeeping and settlements of tokenized crypto assets. Financial intermediaries, or custodians, directly participate in the maintenance of the system by auditing exchange process, and by voting during sidechain-to-D3 tokenization process.

Hyperledger Iroha is D3 ledger, which is used for voting (via multisignature accounts) and decentralized data storage.

This release has the following features:

• Update Iroha to RC2.

• Bitcoin deploy notes (#319)

• Boot repackage was disabled (#315)

• add more logs to eth registration

• add more logs to eth registration

• Bitcoin rollback (#321)

• Bitcoin rollback in case of network failures (#323)

• Bitcoin multisig address safe time source (#325)

• Ignoring failed Iroha account creation command (#324)

• Kill deposit if Iroha is not functioning (#326)

• add automatic relay deployment logic

• Separate shadow jar (#327)

• optimized import

• fix config helper

• add Sora iroha account to genesis and tests for Sora integration

• fix dogecoin precision (actual 9)

• rename getAccountAsset -> getAccountAssetBalance

• change getAccountAssets -> getIrohaAccountBalance

• Bitcoin dynamic fee rate (#329)

• Feature/healthcheck (#333)

• Add readme

• Add healthcheck endpoints

• Fix test compiler error

• Port increment

• Remove registration endpoint

• Transition to IPJ, Iroha rc2 version update (#335)

• Feature/iroha pure java (#307)

• move crypto to Iroha Pure Java library

• Transition to IPJ, Iroha rc2 version update (#330)

• Transition to IPJ

• Iroha rc1 update

• Test fixes

• Iroha rc2 update

• Updated permissions, roles, testing account

• Test fixes

• Update batches

• Fixed status streaming and batch testing

• Switched to ordered batches and to Query API of IPJ

• More queries refactoring, changed wrapper

• Unit tests fixes

• Ignored one more unit test

• Integration tests fixes

• fixup! Integration tests fixes

• fixup! Integration tests fixes

• fixup! fixup! Integration tests fixes

• Config test repaired

• Environment variables configs (#336)

• Added prioritized environment variables config loading

• Fixed working directory of eth services (#338)

• Fixed notary pub key (#340)

• Fixed notary pub key

• Deleted unused notary keys

• fix 'mkdir -p' in Jenkins build-logs (#341)

• Bitcoin services stabilization after migration to IPJ (#342)

• Automatic BTC addresses generation (#337)

• Bitcoin-cli in gradle (#344)

• Feature/tester permissions (#343)

• add permissions for tester account

• fix duplication of can_read_assets

• Fixed PeerGroup.stop()

• Fixing IPJ listener bug (#346)

• Relevant docker files (#345)

• Updated docker files, added bitcoin services

• Deleted variables

• Fixed jenkinsfile variables names

• Fixed main classes

• Fix wait for iroha bug (#348)

• Fix wait for iroha bug

• Add network to dev

• Fix typo

• Fix btc docker. Move dw and address geneartion from single to full (#349)

• Email notifications

• Added build commands to Jenkinsfile (#351)

• Feature/registration (#334)

• Fixed message

• Fixing build (#352)

• Fixed peer group close() (#354)

• SMTP dumbster integration test (#355)

Decentralized Digital Depository v0.2.0-alpha

Distributed Digital Depository is a service platform for decentralized safekeeping and settlements of tokenized crypto assets. Financial intermediaries, or custodians, directly participate in the maintenance of the system by auditing exchange process, and by voting during sidechain-to-D3 tokenization process.

Hyperledger Iroha is D3 ledger, which is used for voting (via multisignature accounts) and decentralized data storage.

This release has the following features:

Bitcoin support

D3 clients can deposit, withdraw and exchange bitcoin assets. Clients get personal bitcoin address during registration in order to deposit bitcoin.

Administration panel

Administration panel allows to overview and control the system.

Multisig

A client can add multiples keys and set quorum in order to sign transactions with multi-signature accounts.

Settlements

Clients can send requests to exchange to other clients. Settlement requests can be cancelled, approved or rejected.

Reports

Clients can overview report on portfolio over some time.

Decentralized Digital Depository v1.0-alpha

Distributed Digital Depository is a service platform for decentralized safekeeping and settlements of tokenized crypto assets. Financial intermediaries, or custodians, directly participate in the maintenance of the system by auditing exchange process, and by voting during sidechain-to-D3 tokenization process.

Hyperledger Iroha is D3 ledger, which is used for voting (via multisignature accounts) and decentralized data storage.

This release has the following features:

Registration of user accounts

D3 clients can create accounts (via the web application) in order to use the system. During this process, each client gets their personal address (of a relay smart contract) in Ethereum, which is used for Ether and ERC20 funds depositing.
Note: In Alpha version relay smart contracts have to deployed manually in advance so that during registration process their addresses are linked to D3 blockchain accounts.

Decentralized deposit of Ether and ERC20 tokens

Any D3 client can deposit funds to their personal Ethereum address. Deposits for such addresses are independently monitored by notaries, which send their part of a multisignature transaction to the D3 blockchain, where they have a shared account for token creation and sending to D3 clients.

Decentralized withdrawal of Ether and ERC20 tokens

In order to get their funds back, D3 clients can create a withdrawal request, which is noticed by notaries. Each notary provides a cryptographic proof, that is validated by master smart contract (this contract is owned by the notaries). In the end, a client gets the funds back if the 2/3rds of notaries singed-off this request.

Internal transfers without any fees

By the means of D3 blockchain API, clients can send each other funds without any transaction fees.

Whitelists for Ethereum withdrawal addresses

As an additional security setting, during the registration process, D3 clients are asked to set a whitelist of Ethereum addresses, that are allowed to get funds back from the D3 client account. Each notary checks whitelist settings, as well as master smart contract, deployed in Ethereum.

Stay tuned for the news!