Update fip-0064.md

[Tanisha-fil]

Changed the status from "Draft" to "Withdrawn" as the author has confirmed limited bandwidth to champion this any further.

Are you drafting a new FIP?

Please follow these guidelines to help ensure that your proposal is set up for success in the governance process.

Open a discussion topic

Changes to the Filecoin core protocol proceed through open discussion.
Please open a new discussion topic in the FIPs repository discussion board and outline you motivation and proposal.

The FIP format is suitable for specifying a concrete protocol change for implementation,
but your discussion post should describe more of the background and problem to be solved,
outline a range of approaches and their tradeoffs, and invite participants to explore other solutions.

Historically, failing to gain some community buy-in before submitting a FIP has often resulted in
rejected FIPs and much wasted effort.

Please use the template

Please draft your FIP by starting with an appropriate template file from templates directory.
Do not significantly change the header table format or section headings.

Don't claim a FIP number

FIP numbers are allocated by the FIP editors when a draft is ready to be merged into the master branch.
The editors coordinate to ensure allocations to in-flight drafts don't collide.
Please do not allocate yourself a FIP number.

Name your file fip-my_draft_title.md (replacing the suffix with an abbreviated title)
and leave "to be assigned" for the FIP number in the header table.
A FIP editor will either inform you of the appropriate number, or insert it themselves when merging.

Please add your FIP to the README

The top-level README.md file contains a table of all FIPs.
Please add yours there in the same PR that adds the FIP draft itself.
Use XXXX for the FIP number until it is assigned by an editor.

Delete this guidance and describe your FIP

Once you've followed the guidance above and are ready to submit your FIP draft,
please delete this text and replace it with a copy of the Abstract from your draft,
and a link to the relevant discussion forum topic.

[rvagg]

Changed the status from "Draft" to "Withdrawn" as the author has confirmed limited bandwidth to champion this any further.

Link to this withdrawal if it's publicly accessible would be helpful for reviewers to validate

[jsoares]

Changed the status from "Draft" to "Withdrawn" as the author has confirmed limited bandwidth to champion this any further.

Link to this withdrawal if it's publicly accessible would be helpful for reviewers to validate

The FIP process spec continues to lack a mechanism for marking a draft as abandoned, in the sense that, for any reason, it is no longer being pursued. This problem comes up once in a while.

Ultimately, I don't think it matters much if an author affirmatively disavows a FIP or if it's just been languishing in draft status for 2 years; we should have a way to indicate to the community that a certain change is no longer being explored. And we should do it consistently.

I'm fine with taking Tanisha's word here given the absence of any evidence that this is still being pursued, but I'd rather see us clean things up more intentionally.

[Tanisha-fil]

Hello, here is the evidence for future records.

Going forward, I will request the author of the FIP to raise a PR for "withdrawing" so that it acts as a validation mechanism. Thanks for pointing this out!