I hereby claim:
- I am christophersanborn on github.
- I am cxsanborn (https://keybase.io/cxsanborn) on keybase.
- I have a public key ASC496wHc0fks3qwaFi1nJI_69F7Fb0chT09MSgvcjiVAAo
To claim this, I am signing this object:
I hereby claim:
To claim this, I am signing this object:
=========================================================== | |
** Benchmark: Scanning Tx Metadata for Owned Tx Outputs: ** | |
=========================================================== | |
* | |
* Generating 248 red-herring keys to be our 'non-matches': | |
* ...Allocated 248 keys in 47 milliseconds. | |
* | |
* Generating Bob StealthAddress: | |
* ...Bob: BTS6zGhuzLcn2YcXoyhdcFvCuH5FT1sr52ceAr7YxzkWp38csK3DAnPmqnSPEXYBn2FkvYNcdGrCnKm497kjaDFPDPjGfZjJqP | |
* |
=========================================================== | |
** Benchmark: Scanning Tx Metadata for Owned Tx Outputs: ** | |
=========================================================== | |
* | |
* Generating 398 red-herring keys to be our 'non-matches': | |
* ...Allocated 398 keys in 73 milliseconds. | |
* | |
* Generating Bob StealthAddress: | |
* ...Bob: BTSBBirtYbXSx7WkCq7sFvAUEJRtj9vCM4LHEEstrGgHmjPjRVohqDWSEBdk3dE1rq1qo7owC2U4mZMFFZbKNxZFQmoWg73Dav | |
* |
=========================================================== | |
** Benchmark: Scanning Tx Metadata for Owned Tx Outputs: ** | |
=========================================================== | |
* | |
* Generating 248 red-herring keys to be our 'non-matches': | |
* ...Allocated 248 keys in 399 milliseconds. | |
* | |
* Generating Bob StealthAddress: | |
* ...Bob: BTS6B1ALhfjYwYW45XeVBfTNL1uFKRwXc21bHenH7rxvAGduVtCbHeJefk91cc3K1xJwLEtVkwxCdfEdCXK4C6xxa2Ls1JxvMS | |
* |
{"method": "call", "params": [2, "broadcast_transaction", [{ "ref_block_num": 55627, "ref_block_prefix": 1486988140, "expiration": "2018-12-17T06:46:00", "operations": [[ 0,{ "fee": { "amount": 10420, "asset_id": "1.3.0" }, "from": "1.2.1152699", "to": "1.2.1152620", "amount": { "amount": 500000, "asset_id": "1.3.0" }, "extensions": [] } ] ], "extensions": [], "signatures": [ "204ef3012212680998c674d5f9078f28f28547e0ef6fff2dca4a2f8d2563a78392331c9c5af6989511220aa25ca22686ec9b61a6a84a2da537f9324cb2043b97f0" ]}]], "id": 4} | |
< {"id":4,"jsonrpc":"2.0","error":{"code":1,"message":"missing required active authority: Missing Active Authority 1.2.1152699","data":{"code":3030001,"name":"tx_missing_active_auth","message":"missing required active authority","stack":[{"context":{"level":"error","file":"transaction.cpp","line":295,"method":"verify_authority","hostname":"","thread_name":"th_a","timestamp":"2018-12-16T07:27:30"},"format":"Missing Active Authority ${id}","data":{"id":"1.2.1152699","auth":{"weight_threshold":1 |
This is a preview release intended for developers, specifically wallet integrators, i.e. authors of GUI wallets or key managers that wish to implement support for the Ledger Nano S into their own projects.
This is NOT a "stable" or "production-ready" release, and should only be installed on devices intended for testing purposes, initialized with a throwaway wallet seed, and which are not being used to hold significant funds.
Ledger-App-BitShares provides the back-end app that runs on the Ledger Nano S hardware wallet. It does not provide a user-friendly front-end for a good user experience.
Goal: To be able to compile Ledger Nano S apps, load them onto a Ledger Nano S, and interact with those apps entirely from within Raspbian running on a Raspberry Pi. This would be one alternative to running a Ledger Nano dev environment from a virtual machine, as is currently needed if you are devloping from a Windows or Mac OS based host machine.
According to here, Nano development uses both GCC and Clang toolchains, with each serving a slightly different purpose:
- A standard ARM gcc to build the non-secure (STM32) firmware and link the secure (ST31) applications
- A standard ARM clang above 4.0.0 with ROPI support to build the secure (ST31) applications
So, if I'm interpretting correctly (iffy), the actual apps we build will compile with Clang, (they're ST31 apps), but the GCC toolchain is still needed for linking, (and additionally for compiling ST32 firmware, if for some reason we are doing that).