Pre-1.0 tasks remaining #35
Comments
I looked at the Signify file format, and it appears that while both |
For base64 decoding, I can just invoke the functions in libsodium via FFI; libsodium is ubiquitous enough that we can assume any target system will have it. |
@DemiMarie I would suggest not making any assumptions about target system if possible. |
@kirushik worth noting that only the signer code would be linked with libsodium, so the scenario you mentioned can’t happen. That said, your point still stands. |
As far as the instructions are concerned, so long as one uses Polkadot{.js} to set up the accounts, it is fairly self-explanatory. |
I disagree with this, but I also realise that a) I am likely exceptionally n00b when considering the users of this software and b) we can wait until a later date and collect feedback on what the actual stumbling blocks users encounter are. |
Update: all automated tests pass and I was able to do basic staking operations. The ones I did not test were:
|
I'm using this issue to track and prioritise the "all small things remaining" sort of tasks which need to be done to call Ledgeracio mature enough for 1.0 release.
Those are extracted from @dvdplm's meeting notes with some minor wording changes, and are ordered by priority highest-first.
--dev
chains[patch]
sections and what are the conditions are for removing themThe text was updated successfully, but these errors were encountered: