2 Commits (3ff2f756368f2d8ec0d1d9d25f6ba9cdabd7383e)

Author	SHA1	Message	Date
Viktor Trón	bfce00385f	Kademlia refactor (#17641) ... * swarm/network: simplify kademlia/hive; rid interfaces * swarm, swarm/network/stream, swarm/netork/simulations,, swarm/pss: adapt to new Kad API * swarm/network: minor changes re review; add missing lock to NeighbourhoodDepthC	6 years ago
ethersphere	e187711c65	swarm: network rewrite merge	7 years ago
ΞTHΞЯSPHΞЯΞ	4d300e4dec	swarm: plan bee for content storage and distribution on web3 ... This change imports the Swarm protocol codebase. Compared to the 'swarm' branch, a few mostly cosmetic changes had to be made: * The various redundant log message prefixes are gone. * All files now have LGPLv3 license headers. * Minor code changes were needed to please go vet and make the tests pass on Windows. * Further changes were required to adapt to the go-ethereum develop branch and its new Go APIs. Some code has not (yet) been brought over: * swarm/cmd/bzzhash: will reappear as cmd/bzzhash later * swarm/cmd/bzzup.sh: will be reimplemented in cmd/bzzup * swarm/cmd/makegenesis: will reappear somehow * swarm/examples/album: will move to a separate repository * swarm/examples/filemanager: ditto * swarm/examples/files: will not be merged * swarm/test/*: will not be merged * swarm/services/swear: will reappear as contracts/swear when needed	8 years ago
Felix Lange	d04a2e7557	all: update license information	9 years ago
Jeffrey Wilcke	f0cbebb19f	core: added basic chain configuration ... Added chain configuration options and write out during genesis database insertion. If no "config" was found, nothing is written to the database. Configurations are written on a per genesis base. This means that any chain (which is identified by it's genesis hash) can have their own chain settings.	9 years ago
Jeffrey Wilcke	342ae7ce7d	core, core/vm, tests: changed the initialisation behaviour of the EVM ... The EVM was previously initialised and created for every CALL, CALLCODE, DELEGATECALL and CREATE. This PR changes this behaviour so that the same EVM can be used through the session and beyond as long as the Environment sticks around.	9 years ago
Jeffrey Wilcke	b6d88a0e9f	core, core/vm, crypto: fixes for homestead ... * Removed some strange code that didn't apply state reverting properly * Refactored code setting from vm & state transition to the executioner * Updated tests	9 years ago