bee VS lotus

Deployed Bee to the mainnet (v1.14.1).

Are you mixing up projects? https://www.ethswarm.org/

You can download the most recent bee packages here: https://github.com/ethersphere/bee/releases/latest

February was a big month for the Swarm network. The price of postage stamps has been recalibrated with the release of Bee 1.20, which marks a major milestone for Swarm’s self-sustaining network. The Research Track has also completed the documentation for Phase 4, which details the work of this phase of the Storage incentives roadmap.

There is a project called Swarm that does exactly this.

https://www.ethswarm.org

(Disclosure: I am working on the project)

https://www.ethswarm.org/ is like storj (stores the file as chunks of data) but more secure and censorship resistant.

In short, there will be five phases to the upgrade (you can expect a more detailed blog on the topic soon). Phase 1 started on 13 September with the breaking release of Bee 1.8.0. This phase will be followed by four other phases that will upgrade the storage incentives mechanism, recalibrate the network, change the storage price, introduce a decentralised price oracle and improve the overall state of the network.

There were two versions of the Bee client released in the last month. It is important to mention that node operators are requested to update to the latest version (1.7.0) as soon as possible because there was a change in the protocol.

I don't mine it myself but check here: https://github.com/filecoin-project/lotus/discussions/5989

Lotus Docs - https://lotus.filecoin.io

It's challenging but if you're interested in doing it I recommend reading some of the specs that the community is experimenting with https://github.com/filecoin-project/lotus/discussions/6071 and reading the documentation https://docs.filecoin.io/mine/lotus/

If you're interested in Filecoin mining you should check out this community thread around people experimenting with miner configurations. https://github.com/filecoin-project/lotus/discussions/6071

"Filecoin developers have opened a GitHub issue to work on a fix. In correspondence with CoinDesk, they denied that the flaw resulted from an RPC error and instead claimed it originated from a mistake on Binance’s end.

API Usage Misunderstanding. The confusion is that when StateGetReceipt is called on the two similar messages (one of which is executed, and the other of which is skipped), it will provide the same result: both corresponding to the message that was executed. This is admittedly counter-intuitive, but intended, behavior. The primary use-case of the StateGetReceipt method is in the event handler used by the Lotus Miner and deal-making process. In the event of a replaced message, these modules do not care if the returned receipt corresponds to the original message, or a replacement one — they simply want to know if the message successfully executed on chain. We have added clarification to the documentation here: https://github.com/filecoin-project/lotus/pull/5838.

Notes: 1. The FIL and KAVA network upgrade & hard fork will not result in new tokens being created. 2. Trading and inter-user transfer of FIL and KAVA trading pairs on CoinEx will not be affected during this period. 3. We will notify users in a further announcement once we deem the upgraded network to be stable. Please refer to the following links for more information: v1.5.0 Release and Upgrade Timeline #5617 Kava-5 Upgrade Instructions