You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is not brainstorming ideas. If you have an idea you'd like to discuss, please open a new discussion on the lotus forum and select the category as Ideas.
I have a specific, actionable, and well motivated feature request to propose.
Lotus component
lotus daemon - chain sync
lotus fvm/fevm - Lotus FVM and FEVM interactions
lotus miner/worker - sealing
lotus miner - proving(WindowPoSt/WinningPoSt)
lotus JSON-RPC API
lotus message management (mpool)
Other
What is the motivation behind this feature request? Is your feature request related to a problem? Please describe.
At the moment, listing all value transfers within a tipset requires:
Calling StateCompute on the tipset.
Walking the trace to find all non-reverted sends with non-zero value transfers.
This can make it difficult to track internal transfers without a deep understanding of Filecoin.
Describe the solution you'd like
I'd like an API like the following:
type Transfer struct {
From ActorID
To ActorID
}
type TransferFilter struct {
From []address.Address
To []address.Address
}
func ChainTransfers(ctx context.Context, ts types.TipSetKey, filter *TransferFilter) -> ([]Transfer, error);
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
Checklist
Ideas
.Lotus component
What is the motivation behind this feature request? Is your feature request related to a problem? Please describe.
At the moment, listing all value transfers within a tipset requires:
This can make it difficult to track internal transfers without a deep understanding of Filecoin.
Describe the solution you'd like
I'd like an API like the following:
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: