FIP: Filecoin Message Replay Protection

[q9f]

Discussion to: #301

Summary: Defines Filecoin chain identifiers and adds them to unsigned messages and signatures to prevent transactions to be replayed across different Filecoin networks.

Note: I'm new to Filecoin and might have missed something in the specification. Feel free to point to everything I should now.

[jleni]

included my comment in #301

[kaitlin-beegle]

Hey @q9f! Perhaps I missed the thread- can I ask why you closed this FIP? Do you no longer plan to work on it?

[q9f]

It hasn't been accepted as a draft and I considered it no longer desired.

[raulk]

I think this draft should be merged. The lack of replay protection becomes even more important with user-programmability and user wallets interacting directly with on-chain actors.

[kaitlin-beegle]

@q9f as long as you don't disagree, I'm reopening this issue. It simply hadn't been merged because FIP editors hadn't been able to provide feedback yet.

Oftentimes, PRs stay open until multiple rounds of revision have taken place. However, FIP editors have all been pretty heads-down on the FVM FIPs. Replay protection may not be an immediate priority, but it's still important.

In general, we are quite capacity limited, and governance topics intentionally move quite slowly. If you have questions or want to push on us, please do so! But no need to close issues and PRs- if the idea wasn't viable, you would know.

[q9f]

Ok, that's fine. Maybe, I just misunderstood the process. I thought assigning a number and merging a draft is a no-brainer.