gaspersic/go-ethereum
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

docs: fix links in dapps pages (#21995)

Browse Source 
* docs: fix links in dapps pages

* Update docs/_dapp/tracing.md

Co-authored-by: Martin Holst Swende <martin@swende.se>
This commit is contained in:
Sina Mahmoodi
2020-12-27 22:40:20 +01:00
committed by GitHub
parent 29ba68fed9
commit a1a1ec5d45
2 changed files with 8 additions and 19 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
docs/_dapp/native-accounts.md
View File

@ -45,14 +45,9 @@ environments.
*For those interested in the cryptographic and/or implementation details, the key-store *For those interested in the cryptographic and/or implementation details, the key-store
uses the `secp256k1` elliptic curve as defined in the [Standards for Efficient uses the `secp256k1` elliptic curve as defined in the [Standards for Efficient
Cryptography](sec2), implemented by the [`libsecp256k`](secp256k1) library and wrapped by Cryptography](http://www.secg.org/sec2-v2.pdf), implemented by the [`libsecp256k`](https://github.com/bitcoin-core/secp256k1) library and wrapped by
[`github.com/ethereum/go-ethereum/accounts`](accounts-go). Accounts are stored on disk in [`github.com/ethereum/go-ethereum/accounts`](https://godoc.org/github.com/ethereum/go-ethereum/accounts). Accounts are stored on disk in
the [Web3 Secret Storage](secstore) format.* the [Web3 Secret Storage](https://github.com/ethereum/wiki/wiki/Web3-Secret-Storage-Definition) format.*
[sec2]: http://www.secg.org/sec2-v2.pdf
[accounts-go]: https://godoc.org/github.com/ethereum/go-ethereum/accounts
[secp256k1]: https://github.com/bitcoin-core/secp256k1
[secstore]: https://github.com/ethereum/wiki/wiki/Web3-Secret-Storage-Definition
### Keystores from Go ### Keystores from Go

16
docs/_dapp/tracing.md
View File

@ -105,8 +105,8 @@ that take the above form:
### Generating basic traces ### Generating basic traces
To generate a raw EVM opcode trace, `go-ethereum` provides a few [RPC API To generate a raw EVM opcode trace, `go-ethereum` provides a few [RPC API
endpoints](debug-api), out of which the most commonly used is endpoints](../rpc/ns-debug), out of which the most commonly used is
[`debug_traceTransaction`](trace-tx). [`debug_traceTransaction`](../rpc/ns-debug#debug_tracetransaction).
In its simplest form, `traceTransaction` accepts a transaction hash as its sole argument, In its simplest form, `traceTransaction` accepts a transaction hash as its sole argument,
traces the transaction, aggregates all the generated data and returns it as a **large** traces the transaction, aggregates all the generated data and returns it as a **large**
@ -125,7 +125,7 @@ $ curl -H "Content-Type: application/json" -d '{"id": 1, "method": "debug_traceT
``` ```
Running the above operation on the Rinkeby network (with a node retaining enough history) Running the above operation on the Rinkeby network (with a node retaining enough history)
will result in this [trace dump](rinkeby-example-trace-big). will result in this [trace dump](https://gist.github.com/karalabe/c91f95ac57f5e57f8b950ec65ecc697f).
### Tuning basic traces ### Tuning basic traces
@ -157,7 +157,7 @@ $ curl -H "Content-Type: application/json" -d '{"id": 1, "method": "debug_traceT
``` ```
Running the above operation on the Rinkeby network will result in this significantly Running the above operation on the Rinkeby network will result in this significantly
shorter [trace dump](rinkeby-example-trace). shorter [trace dump](https://gist.github.com/karalabe/d74a7cb33a70f2af75e7824fc772c5b4).
### Limits of basic traces ### Limits of basic traces
@ -197,7 +197,7 @@ Here's what happens in each respective case:
4. Does not need to replay anything, can immediately load up the state and serve the request. 4. Does not need to replay anything, can immediately load up the state and serve the request.
There is one other option available to you, which may or may not suit your needs. That is There is one other option available to you, which may or may not suit your needs. That is
to use [Evmlab](evmlab). to use [Go-evmlab](https://github.com/holiman/goevmlab).
docker pull holiman/evmlab && docker run -it holiman/evmlab docker pull holiman/evmlab && docker run -it holiman/evmlab
@ -208,9 +208,3 @@ transaction touches (balances, code, nonce etc). It should be mentioned that the
reproducer is strictly guaranteed to be totally exact with regards to gascosts incurred by reproducer is strictly guaranteed to be totally exact with regards to gascosts incurred by
the outer transaction, as evmlab does not fully calculate the gascosts for nonzero data the outer transaction, as evmlab does not fully calculate the gascosts for nonzero data
etc, but is usually sufficient to analyze contracts and events. etc, but is usually sufficient to analyze contracts and events.
[evmlab]: https://github.com/holiman/evmlab
[rinkeby-example-trace]: https://gist.github.com/karalabe/d74a7cb33a70f2af75e7824fc772c5b4
[rinkeby-example-trace-big]: https://gist.github.com/karalabe/c91f95ac57f5e57f8b950ec65ecc697f
[debug-api]: ../rpc/ns-debug
[trace-tx]: ../rpc/ns-debug#debug_tracetransaction