-
Hello,
I'm very interested in reducing the barriers to new developers join NEO, and one thing that I often see is that that we currently depend on windows machines to be able to setup a private net…
lock9 updated
5 years ago
-
Hello,
I would like to start a discussion about changing the current documentation structure.
Here is how it is today:
https://www.dropbox.com/s/xjrvx037yjtz7iz/current-docs.png?dl=0
I think t…
lock9 updated
4 years ago
-
### Expected behavior
In the accounts entity, the public keys associated with the multisignature account are stored in the `memberPubicKeys` property. Therefore, when applying a multisignature transa…
-
We do not need to be computing the address of the multisignature wallet via a deploy transaction anymore. Instead, let's use CREATE2 and have the CREATE_CHANNEL method return the computed address afte…
-
An `OpenMultiSig` lists a MultiSignature account in the ledger. The validation logic for a `OpenMultiSig` transaction must do the following:
- Check that the creator address exists.
- Check that t…
-
One useful feature, already proposed for Neo 2 (https://github.com/neo-project/neo/issues/700 but now not in schedule for implementation) is the ability to check multiple witness in a "multisig" forma…
-
tfchain implements multisignature functionality, this is useful for other chains as well so it would be good to put it in the Rivine extensions package.
-
azban updated
5 years ago
-
### Expected behavior
The properties defined for account related to multisignatures should be in camel case.
### Actual behavior
The multisignature transaction assigns these properties to account …
-
### Expected behavior
The `chain` module should only have standard transactions required to run the DPOS system, register the second signature and multisignature accounts:
- type 0
- type 1
- type…