-
Notifications
You must be signed in to change notification settings - Fork 15
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
Separate distribution and signing in Wallet interface #230
Milestone
Comments
4 tasks
olemis
added a commit
to simelo/fibercryptowallet
that referenced
this issue
Dec 6, 2019
olemis
added a commit
to simelo/fibercryptowallet
that referenced
this issue
Dec 6, 2019
…e.Wallet => core.FullWallet
olemis
added a commit
to simelo/fibercryptowallet
that referenced
this issue
Dec 6, 2019
…t interface types
olemis
added a commit
to simelo/fibercryptowallet
that referenced
this issue
Dec 9, 2019
olemis
added a commit
to simelo/fibercryptowallet
that referenced
this issue
Dec 9, 2019
… separate Wallet contract
olemis
added a commit
to simelo/fibercryptowallet
that referenced
this issue
Feb 11, 2020
…ace into smaller interfaces
olemis
added a commit
to simelo/fibercryptowallet
that referenced
this issue
Feb 11, 2020
olemis
added a commit
to simelo/fibercryptowallet
that referenced
this issue
Feb 12, 2020
…interfaces for transaction signing - SignServicesForTxn receives Wallet instead of FullWallet - LoadTransactionAPI returns BlockchainVisor - ReadyForTxn receives Wallet instance as first argument
olemis
added a commit
to simelo/fibercryptowallet
that referenced
this issue
Feb 12, 2020
... BlockchainExplorer, BlockchainVisor, Wallet, WatchWallet
olemis
added a commit
to simelo/fibercryptowallet
that referenced
this issue
Feb 12, 2020
…ddress methods
olemis
added a commit
to simelo/fibercryptowallet
that referenced
this issue
Feb 12, 2020
…mpleWalletOutput and SimpleWalletAddress
olemis
added a commit
to simelo/fibercryptowallet
that referenced
this issue
Feb 12, 2020
…isor - Transfer not supported - ScanOutputs not implemented
olemis
added a commit
to simelo/fibercryptowallet
that referenced
this issue
Feb 12, 2020
…sactionAPI ... core.BlockchainTransactionAPI => core.BlockchainVisor
This was referenced Feb 13, 2020
olemis
added a commit
to simelo/fibercryptowallet
that referenced
this issue
Feb 13, 2020
…mplement DeriveParentPubKey
olemis
added a commit
to simelo/fibercryptowallet
that referenced
this issue
Feb 13, 2020
…erface - ReadyForTxn receives Wallet instead of FullWallet - GetLoadedAddressesForAccount added but not implemented - GetAllLoadedAddresses added but not implemented, and returns error - GenAddresses returns error - Add ErrInvalidArgument, and ErrInvalidAccount error conditions
olemis
added a commit
to simelo/fibercryptowallet
that referenced
this issue
Feb 13, 2020
olemis
added a commit
to simelo/fibercryptowallet
that referenced
this issue
Feb 13, 2020
…ng addresses in checkEquivalentSkycoinWallets
olemis
added a commit
to simelo/fibercryptowallet
that referenced
this issue
Feb 13, 2020
… v2 API changes
olemis
added a commit
to simelo/fibercryptowallet
that referenced
this issue
Feb 13, 2020
olemis
added a commit
to simelo/fibercryptowallet
that referenced
this issue
Feb 13, 2020
olemis
added a commit
to simelo/fibercryptowallet
that referenced
this issue
Feb 13, 2020
…t v2 API changes
olemis
added a commit
to simelo/fibercryptowallet
that referenced
this issue
Feb 13, 2020
…impleWalletOutput ... since there is neither WalletAddress nor WalletOutput no more
olemis
added a commit
to simelo/fibercryptowallet
that referenced
this issue
Feb 13, 2020
…WalletGenAddresses
olemis
added a commit
to simelo/fibercryptowallet
that referenced
this issue
Feb 13, 2020
…estRemoteWalletGenAddresses
olemis
added a commit
to simelo/fibercryptowallet
that referenced
this issue
Feb 13, 2020
…se wallet v2 API
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Feature description
Refactor
core.Wallet
interface for v2.Is your feature request related to a problem? Please describe.
Address distribution , transaction creation and signing are altogether in
core.Wallet
interface. Besides the last two are quite similar to muiti-wallet API .Describe the solution you'd like
Separate them three wallet aspects so that specialized concrete types may be built.
Describe alternatives you've considered
Keeping wallet contract in v1 API creates friction and duplication when trying to move forward.
Possible implementation
The text was updated successfully, but these errors were encountered: