-
Notifications
You must be signed in to change notification settings - Fork 20.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot read property 'createsContract' of undefined #134
Milestone
Comments
obscuren
added a commit
that referenced
this issue
Oct 22, 2014
nonsense
added a commit
to nonsense/go-ethereum
that referenced
this issue
Nov 22, 2017
p2p/simulations: tcp pipe
ngtuna
added a commit
to ngtuna/tomochain
that referenced
this issue
Aug 16, 2018
remove nodeId in smart contract
tony-ricciardi
pushed a commit
to tony-ricciardi/go-ethereum
that referenced
this issue
Jan 20, 2022
* cmd, consensus, eth, ethstats: add protocol interface into consensus to support custom messages * params: add Istanbul consensus engine config to ChainConfig * cmd/*: add Istanbul command line flags * consensus/istanbul, eth: add Istanbul configuration * node: add an interface to retrieve node key from config * core/types: add Istanbul specific block hash calculation * internal/web3ext: add Istanbul JS RPC API * consensus: add Istanbul consensus engine interface * consensus/istanbul: Istanbul core implementation * consensus/istanbul: add tests for Istanbul core * consensus/istanbul: common Istanbul interfaces and types * consensus/istanbul: Istanbul validator set implementation * consensus/istanbul: Istanbul consensus backend implementation * core, les, eth, miner: Istanbul consensus integration * cmd/*, core, params: add ottoman testnet * Address comments * Fix Istanbul lint (ethereum#137) * Remove unused vars for lint * Remove unnecessary conversion * Don't propose empty blocks with Istanbul (ethereum#134) * Make istanbul.Backend a public type * Don't mine empty block with Istanbul engine unless necessary * PR comments * Revert to original order * Add test fixes * PR comments * Update the expected hash given that celo headers have a different payload with BlockSignature * Make Istanbul's Seal asynchronous Originally, when Istanbul was written, the Seal method was synchronous, i.e. it would return when the sealing process was done (or cancelled). Now that is no longer the case, in fact the miner expects the Seal to return to be able to respond/intiate other Seal's. This commit allows Istanbul to do so. * Notify the Istanbul engine of new ChainHeads During the merge, we removed this crucial line, where the worker will notify the Istanbul engine of new chain heads that crucially allow its peers to increse the sequence number for the next Seal. * Apply celolatest syncmode mods to Istanbul * [Istanbul] Seal/NewHeadChain fixes (ethereum#147) * Make Istanbul's Seal asynchronous Originally, when Istanbul was written, the Seal method was synchronous, i.e. it would return when the sealing process was done (or cancelled). Now that is no longer the case, in fact the miner expects the Seal to return to be able to respond/intiate other Seal's. This commit allows Istanbul to do so. * Notify the Istanbul engine of new ChainHeads During the merge, we removed this crucial line, where the worker will notify the Istanbul engine of new chain heads that crucially allow its peers to increse the sequence number for the next Seal. * Fix test * Fix test
joshuacolvin0
pushed a commit
to joshuacolvin0/go-ethereum
that referenced
this issue
Jan 4, 2023
…zation Fix Deposit deserialization
weiihann
pushed a commit
to weiihann/go-ethereum
that referenced
this issue
Feb 23, 2023
disable memory trace
come-maiz
pushed a commit
to come-maiz/go-ethereum
that referenced
this issue
Sep 19, 2024
ci: fix ci error
s1na
pushed a commit
to s1na/go-ethereum
that referenced
this issue
Dec 2, 2024
Update trc21_reader.go
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm using version from git: 41ae6f2 and I get:
when trying to create a contract
The text was updated successfully, but these errors were encountered: