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
..
call.go	Handle worker key changes correctly in runtime	2020-10-24 02:57:17 -07:00
forks_test.go	fix import of v0 for test	2020-10-21 12:18:38 -07:00
forks.go	optimize code UpgradeTapeHeight and go fmt	2020-11-19 14:47:13 +08:00
read.go	Get State API almost working	2020-09-17 05:05:32 -04:00
stmgr.go	Modify vesting schedule post-calico	2020-11-15 19:27:45 -05:00
utils.go	Make state tipset usage consistent in the API	2020-12-09 11:29:40 -08:00