You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Added compatibility with Ian Coleman's BIP39 tool for several input formats:
* `base6`, `base10`, `bits`, and `dice` are now compatible.
* `hex` as an input method is already compatible if used with his tool in "raw entropy" mode.
* `cards` is not compatible as his algorithm is complex and possibly not worth spending the time on.
* Updated MANUAL.md examples to remain accurate.
* Added a section on Compatibility with other tools to MANUAL.md.
`bip39` and `slip39` output formats can be combined with the `random` (default) input format. If the `--count N` option is used with the `hex` input format, it results in a seed of `N` bytes being generated and used.
In this example, the same entropy is used twice in producing a SLIP39 share, which would normally result in two different shares being produced. But by providing `--deterministic FOOBAR`, the same results are produced.
response lunch academic agency activity fiber escape research earth pipeline prevent prepare activity erode grumpy problem justice vampire tension custody
604
+
response lunch academic always crisis cards chemical expect muscle anxiety training thunder climate plan geology bulb scatter teacher gravity guilt
605
+
```
606
+
607
+
## Compatibility
608
+
609
+
* seedtool has been tested to give the same results as [Ian Coleman's BIP39 tool](https://iancoleman.io/bip39/) for the following input methods: `base6`, `base10`, `bits`, and `dice`.
610
+
*`hex` as an input method is already compatible if used with his tool in "raw entropy" mode.
611
+
*`cards` is not currently compatible.
612
+
613
+
The example below can be replicated using Coleman's tool and selecting the following options:
Copy file name to clipboardExpand all lines: README.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -91,7 +91,7 @@ We do ask that you offer us good faith and use best efforts not to leak informat
91
91
92
92
## Reporting a Vulnerability
93
93
94
-
Please report suspected security vulnerabilities in private via email to ChristopherA@LifeWithAlacrity.com (do not use this email for support). Please do NOT create publicly viewable issues for suspected security vulnerabilities.
94
+
Please report suspected security vulnerabilities in private via email to ChristopherA@BlockchainCommons.com (do not use this email for support). Please do NOT create publicly viewable issues for suspected security vulnerabilities.
95
95
96
96
The following keys may be used to communicate sensitive information to developers:
0 commit comments