I accidentally get all my plots in a PC burned, can the protocol/software be changed to prevent this from happening for users/farmers?

Support
1

By accident, I clicked on my farmer instance twice and didn’t notice that for a long time. As a result, I think all my plots in that PC were burned by the protocol. This is my mistake but it’s also really really painful to see my 8TB plots in total gone, just because of the mistake.

In my case, I open 2 farmer instances (again this is my mistake) but both are still connected to the node. So my suggestion is: Can we change the software so that people cannot open the same farmer instance in the same PC (e.g. when a plot is initialized, it’s locked)? We can see that my mistake can happen to other honest farmers. If he were a cheater, at least he would connect to different node or from different PC.

Below is my plot detail in that PC

Single disk farm 0:
  ID: 01HFHS4TGDR6H0G1QWHSP8KMPE
  Genesis hash: 0x418040fc282f5e5ddd432c46d05297636f6f75ce68d66499ff4cbda69ccd180b
  Public key: 0xeceaf96a7ff058e18b7643618b36edd88cab0c2cf2d193b10c29299462a84e3d
  Allocated space: 1.7 TiB (1.9 TB)
  Directory: F:\1
Single disk farm 1:
  ID: 01HFHS4THPYCZ8TY894FTK01QZ
  Genesis hash: 0x418040fc282f5e5ddd432c46d05297636f6f75ce68d66499ff4cbda69ccd180b
  Public key: 0x625cafd9538eaa40738237d93a4854fca0f755fc699e6ff8fd055f8c92bab56f
  Allocated space: 1.5 TiB (1.6 TB)
  Directory: C:\1
Single disk farm 2:
  ID: 01HFHS4TJDG0TPP4GQ7VBAXXYF
  Genesis hash: 0x418040fc282f5e5ddd432c46d05297636f6f75ce68d66499ff4cbda69ccd180b
  Public key: 0xfedef53065b6bde350f1eb59edc29b04ee5e003bee59be089aa463af0c612f51
  Allocated space: 1.7 TiB (1.9 TB)
  Directory: D:\1
Single disk farm 3:
  ID: 01HFHS4TK9ZE4BGZVQRPQ88Z6W
  Genesis hash: 0x418040fc282f5e5ddd432c46d05297636f6f75ce68d66499ff4cbda69ccd180b
  Public key: 0x1af84ae2692bc1b027ffbcb26284583589461409666738d45d62fce1359c7969
  Allocated space: 1.7 TiB (1.9 TB)
  Directory: E:\1
3 Likes
2

Very good suggestion, something that was on my mind for a while as well (I believe there is even a TODO in the code somewhere).

I just created an issue: Prevent the same farm from being opened more than once at a time · Issue #2334 · subspace/subspace · GitHub

This is something that community members should be able to contribute as well and get some reward in return as per Contribution Contest

3 Likes
3

Thanks Nazar for looking into it. This PC is a Win 11 one, not sure why but when I ran the bat file, it’s not popped up. And it must be after I upgraded to new version. It’s a good lesson learn before the mainnet anyway.

And to your suggestion, as much as I wish to, I’m not a coder so I can’t do much. I hope as time goes by, the community will grow and more capability hands will join and contribute.

thanks,

2 Likes
4

I’m sure we’ll fix it before mainnet, but hopefully much sooner :slightly_smiling_face:

5

Add farm locking, preventing multiple farmers from using the same farm concurrently that leads to slashing and other issues by nazar-pc · Pull Request #2344 · subspace/subspace · GitHub implements locking that should prevent this going forward, most likely will be included in the next Gemini 3g release.

2 Likes