forks/go-ethereum
1
0
Fork 1
mirror of https://github.com/ethereum/go-ethereum.git synced 2026-04-14 13:48:37 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 1

Update direct binding from sol to go using abigen

Browse source 
The new abigen version does not have the --solc file to directly bind a Solidity contract to a Go package. This was caused because the solc compiler in ```go-ethereum``` needed to be continuously synchronized with the original solc compiler in order to offer the full features and security of latest versions. The team decided to remove the direct biding functionality from Solidity to Go but the documentation still has it (therefore confusing newcomers with outdated instructions).
This commit is contained in:
Nico Serrano 2022-06-01 15:29:45 -05:00 committed by GitHub
parent b24f4ce8f4
commit 4712997df5
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 8 additions and 21 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

29
docs/_dapp/native-bindings.md
View file

@ -332,30 +332,17 @@ Pending name: Contracts in Go!!!
## Bind Solidity directly ## Bind Solidity directly
If you've followed the tutorial along until this point you've probably realized that In the past, abigen allowed you to compile and bind a Solidity source file directly to a Go package.
every contract modification needs to be recompiled, the produced ABIs and bytecodes This feature has been discontinued from [v1.10.18](https://github.com/ethereum/go-ethereum/releases/tag/v1.10.18)
(especially if you need multiple contracts) individually saved to files and then the onwards due to maintenance synchronization challenges with the compiler in ```go-ethereum```.
binding executed for them. This can become a quite bothersome after the Nth iteration, Now, to bind a Solidity source file into a go package you will have to compile it first using
so the `abigen` command supports binding from Solidity source files directly (`--sol`), any of your prefered compilers (e.g. [solc](https://docs.soliditylang.org/en/v0.8.14/installing-solidity.html)
which first compiles the source code (via `--solc`, defaulting to `solc`) into it's or [Remix](https://remix.ethereum.org/)) and bind it later. Binding the official Token contract [`token.sol`](https://gist.github.com/karalabe/08f4b780e01c8452d989) would then entail to running:
constituent components and binds using that.
Binding the official Token contract [`token.sol`](https://gist.github.com/karalabe/08f4b780e01c8452d989)
would then entail to running:
``` ```
$ abigen --sol token.sol --pkg main --out token.go $ solc --abi --bin token.sol -o tokenDirectory
$ abigen --abi tokenDirectory/token.abi --bin tokenDirectory/token.bin --pkg main --type token --out token.go
``` ```
*Note: Building from Solidity (`--sol`) is mutually exclusive with individually setting
the bind components (`--abi`, `--bin` and `--type`), as all of them are extracted from
the Solidity code and produced build results directly.*
Building a contract directly from Solidity has the nice side effect that all contracts
contained within a Solidity source file are built and bound, so if your file contains many
contract sources, each and every one of them will be available from Go code. The sample
Token solidity file results in [`token.go`](https://gist.github.com/karalabe/c22aab73194ba7da834ab5b379621031).
### Project integration (i.e. `go generate`) ### Project integration (i.e. `go generate`)
The `abigen` command was made in such a way as to play beautifully together with existing The `abigen` command was made in such a way as to play beautifully together with existing