ethereumjs / ethereumjs-blockchain Goto Github PK

As mentioned here, there is still Constantinople referenced as latest HF option in the constructor, this should be updated to Petersburg.

As we've been planning to move over to a monorepo, we can start by migrating their CIs to the same service.

ultimately I would like to remove validation all together and use the iterator like we do in vm.runBlockchain

Hello, my company is developing a ether wallet, ether node has been set up, with the Geth. But now there is a problem, that is, how to query the wallet address under the transaction records. Do you need to parse the node's leveldb file, can you give me some ideas? Thank you.

When I manipulate the test code a bit, using a leveldown instance in a created db folder und running this code twice, the console.log(head) in line 27 on both runs returns the genesis head (so both with <Buffer d7 f8 97 4f b5 ac 78 d9 ac 09 9b 9a d5 01 8b ed c2 ce 0a 72 da d1 82 7a 17 09 da 30 58 0f 05 44> for the stateRoot.

@vpulim Do you know what is going on here? Is this a bug? Could you have a look and test this?

Version 1.0.5 of semaphore just got published.

This version is covered by your current version range and after updating it in your project the build failed.

semaphore is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

Version 4.9.1 of tape was just published.

This version is covered by your current version range and after updating it in your project the build failed.

tape is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

This is associated with the migration to the new ethereumjs-common library and using the migrated version of the block library (see PR below).

Depends on ethereumjs/ethereumjs-block#44.

readme lists:

new Blockchain(blockDB, detailsDB)

but args are

new Blockchain(blockDB, validate)

Version 2.2.0 of async just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As async is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

The NPM package for version 3.3.1 seems to contain older code (3.3.0 I think). It doesn't have the fix that was part of the 3.3.1 changes. Is it possible to re-publish it?

Version 1.4.0 of ethereumjs-block just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As ethereumjs-block is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

If someone could provide a working example on how to use this package to instantiate Blockchain class instance from existing geth data from disk, that would be awesome.

https://github.com/ethereumjs/ethereumjs-blockchain/wiki/Accessing-ethereum-blockchain-object-methods by @shanawarkhan

TAP version 13
# BlockchainTests
# file: ContractCreationSpam_d0g0v0 test: ContractCreationSpam_d0g0v0_EIP158
ok 1 correct pre stateRoot
ok 2 correct genesis RLP
ok 3 last block hash
ok 4 correct header block
# file: badOpcodes_d0g0v0 test: badOpcodes_d0g0v0_EIP158
ok 5 correct pre stateRoot
ok 6 correct genesis RLP
/ethereum/ethereumjs-vm/node_modules/ethereumjs-blockchain/index.js:256
      self.meta.rawHead = blockHashHexString
                        ^

TypeError: Cannot set property 'rawHead' of null
    at rebuildInfo (/ethereum/ethereumjs-vm/node_modules/ethereumjs-blockchain/index.js:256:25)
    at /ethereum/ethereumjs-vm/node_modules/async/dist/async.js:3853:24
    at replenish (/ethereum/ethereumjs-vm/node_modules/async/dist/async.js:946:17)
    at iterateeCallback (/ethereum/ethereumjs-vm/node_modules/async/dist/async.js:931:17)
    at /ethereum/ethereumjs-vm/node_modules/async/dist/async.js:906:16
    at /ethereum/ethereumjs-vm/node_modules/async/dist/async.js:3858:13
    at lookupParentBlock (/ethereum/ethereumjs-vm/node_modules/ethereumjs-blockchain/index.js:202:27)

Reproduce by running blockchain tests in ethereumjs-vm, using the master branch of this repository as a dependency.

• package.json says MPL2.0
• README has no information about this
• but the LICENSE file contains GPL2.0

As reported in ethereumjs/ethereumjs-monorepo#517, this library can't run in the browser because it uses util.callbackify.

Version 2.13.0 of coveralls just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As coveralls is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

Tests are leftover from ethereumjs-lib days and need some love

I just noticed that this lib is using a static fixture, i.e. not tests from ethereumjs-testing and the last commit of that file is in May 2018. I'm not sure if any HF since then has directly touched Blockchain's code, but at least in future it's possible.

The file seems to have been taken from the BlockchainTests suite, but many of the values are hardcoded in the unit tests. Ideally we should make this a bit more flexible and upgrade-able.

when I use these code, it can't run and return crash:

var blockchain = new Blockchain(blockchainDB)
var genesisBlock
genesisBlock = new Block()
genesisBlock.header = new BlockHeader(testData.genesisBlockHeader)
blockchain.putGenesis(genesisBlock, function(){})

the crash log:

      self.meta.rawHead = blockHashHexString
                        ^

TypeError: Cannot set property 'rawHead' of null
    at rebuildInfo (/home/elven/Learn/ethereumjs-blockchain/index.js:257:25)
    at /home/elven/Learn/ethereumjs-blockchain/node_modules/async/dist/async.js:3853:24
    at replenish (/home/elven/Learn/ethereumjs-blockchain/node_modules/async/dist/async.js:946:17)
    at iterateeCallback (/home/elven/Learn/ethereumjs-blockchain/node_modules/async/dist/async.js:931:17)
    at /home/elven/Learn/ethereumjs-blockchain/node_modules/async/dist/async.js:906:16
    at /home/elven/Learn/ethereumjs-blockchain/node_modules/async/dist/async.js:3858:13
    at lookupParentBlock (/home/elven/Learn/ethereumjs-blockchain/index.js:202:27)
    at /home/elven/Learn/ethereumjs-blockchain/node_modules/async/dist/async.js:3853:24
    at replenish (/home/elven/Learn/ethereumjs-blockchain/node_modules/async/dist/async.js:946:17)
    at iterateeCallback (/home/elven/Learn/ethereumjs-blockchain/node_modules/async/dist/async.js:931:17)

Version 5.1.3 of ethereumjs-util was just published.

This version is covered by your current version range and after updating it in your project the build failed.

ethereumjs-util is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

The tests of this library are extremely hard to work with. They are coded as a single tape tests, with lots of shared state between them. I tried to add a new test in #121, and couldn't make it run.

I tried to modernize them today, separating them in multiple tests, and removing the asyn library, but it is very hard to do so. I spent about half an hour on this and got to migrate 5 of ~40 tests, and I suspect they were by far the easiest to migrate, so I suspect this would take at least 4-5hs, and will be difficult to review.

As it will take some time, I'm opening this issue to get your opinion if this is something that we want in the short-term, @holgerd77, @s1na.

Version 4.7.0 of tape just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As tape is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

Documentation of this library should be auto-generated with TypeDoc, this PR ethereumjs/ethereumjs-util#170 can serve as a reference (see also technical docs on documentation).

For this the manual documentation comments in the README (https://github.com/ethereumjs/ethereumjs-account) should be integrated in the code along the way.

Only functionality in index.ts is currently part of the external API and should be publicly exposed (so roughly the currently documented functions, apart from eventually some updates from recent changes or functionality additions).

Since the recent changes in the test suite #134, the Coverage report stopped working, leading to a wrong 0% test coverage result.

It happened for the first time in Travis and it got carried over to the GH actions.

Currently different key types are used:

• number for accessing block numbers
• strings for meta-information such as 'meta', 'detail:' + ,
• buffers in merkle-patricia-tree

I've noticed weird behavior while working with on the persistency feature for ethereumjs-testrpc with leveldown - the persistent storage adapter for levelup: levelup uses red-black-trees to store data with a custom comparison function, if now different key types are used (I could observe this with Buffer and non Buffer keys) data is saved to a different location from where it is looked up for which results in saving data to a key and don't be able to get it again, leading to errors like this: trufflesuite/ganache-cli-archive#81 .
This is (temporary?) resolved by switching to a consistent key type (I refactored ethereumjs-blockchain to work with Buffer keys only).

Should I create a PR for this?

Version 1.3.6 of levelup just got published.

This version is covered by your current version range and after updating it in your project the build failed.

levelup is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

Version 5.1.2 of ethereumjs-util just got published.

This version is covered by your current version range and after updating it in your project the build failed.

ethereumjs-util is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

I'm working on a testing chain with this module and ethereumjs-vm and want to validate everything but POW. The reason I want to do it is that I want to spot every error asap, but I don't want to waste time on POW mining.

The problem is that the only way to disable POW verification is by setting BlockchainOptions#validate to false, and this also disables blocks' validation (i.e. calling block.validate).

I think we should have two separate options for this.

As mentioned here, we should move the example from the actual code into the README.

Version 10.0.1 of standard just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As standard is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

Version 1.2.5 of memdown just got published.

This version is covered by your current version range and after updating it in your project the build failed.

memdown is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

Would it be possible for someone to take a quick look at the issue I've documented here: https://ethereum.stackexchange.com/questions/37691/how-to-use-nodejs-javascript-and-levelup-to-read-blocks-from-local-geth-database.

I don't know if this is my error/misunderstanding or a problem with ethereumjs/blockchain.

Thank you,
Michael Herman (Toronto)

As mentioned here, tsdoc tags should be used.

please bump ethashjs dep to 0.0.4

pending: ethereumjs/ethashjs#3