lotus/node/impl/full
Steven Allen b8e3808c4f Make state tipset usage consistent in the API
_Always_ (almost) use the tipset's parent state, instead of computing.

Exceptions:

* MinerGetBaseInfo. Fixing this would break things so we need to be
careful (although we could bump the API version, fix it, then fix the call
sites).
* StateReplay. This is replaying a message on top of the given tipset.
* GasEstimateGasLimit. This executes the message on-top-of the tipset's
computed state (unlike call which executes it on the tipset's parent state).
  * Having this method and Call apply the message at different heights is really
  weird.
2020-12-09 11:29:40 -08:00
..
beacon.go Draw the rest of the owl 2020-09-10 17:41:55 -04:00
chain.go feat: lite-mode - market storage and retrieval clients 2020-10-23 15:02:26 +02:00
gas_test.go gas: Add tests to median premium math 2020-09-09 12:14:46 +02:00
gas.go Refactor DefaultMessageSendSpec 2020-12-08 20:51:27 +01:00
mpool.go Merge branch 'hunjixin/feat/batchmsg' of github.com:hunjixin/lotus into hunjixin-hunjixin/feat/batchmsg 2020-10-22 14:45:33 +02:00
multisig.go migrate methods to abstracted methods 2020-10-21 12:18:37 -07:00
state.go Make state tipset usage consistent in the API 2020-12-09 11:29:40 -08:00
sync.go Expose WorkerID 2020-10-28 20:22:07 +01:00
wallet.go bonus: fix WalletSign using t0 addresses in WalletSignMessage 2020-11-27 17:19:41 +01:00