Scaleway announces measures against abusive Chia plotting and farming
81–90 of 188 posts
Re: Scaleway announces measures against abusive Chia plotting and farming
#82Earlier quoted context omitted.
I have 512GB Ram, cant it be used for plotting without ssd?
You could. But someone else could add 8 SSD's for the same money and plot multiple times as fast as you, until the SSDs break.
Re: Scaleway announces measures against abusive Chia plotting and farming
#83Somebody needs to invent a coin that works on proof-of-carbon-emission-reductions, or proof-of-global-poverty-reduction and do some real good for the world.
A smart bike that prints coins based on the energy put into the bike.
Re: Scaleway announces measures against abusive Chia plotting and farming
#84Re: Scaleway announces measures against abusive Chia plotting and farming
#85Translation: Scaleway didn't take SSD wear into account when designing their cloud.
Chia farming is allowed on Scaleway Object Storage providing prior request has been both made and authorized by our sales team
Translation: They can't expand their object storage fast enough to keep up with demand.
Re: Scaleway announces measures against abusive Chia plotting and farming
#86Re: Scaleway announces measures against abusive Chia plotting and farming
#87Earlier quoted context omitted.
It’s like proof of stake - you have to prove you have a track record of producing the emissions.
Burn tires for a year then reap the reductions the next.
Re: Scaleway announces measures against abusive Chia plotting and farming
#88Is it possible to optimize plotting to use I/O less and RAM more? Or is it an inherent boundary of the protocol like energy use is in PoW?
If you have ~300 GB of RAM you should be able to plot directly in RAM.
Re: Scaleway announces measures against abusive Chia plotting and farming
#89Re: Scaleway announces measures against abusive Chia plotting and farming
#90> Chia plotting is extremely I/O intensive and destroys most SSDs in under a few weeks I need to look into this more, but I think this is an implementation issue. It should buffer in RAM to require only one write pass. Edit: I was wrong. They set a minimum k that wouldn’t easily fit in ram.