@xiedapao
If there does exist such a thing, I cannot find it.

zenground0 [7 hours ago]
I don't believe there is

zenground0 [7 hours ago]
tho maybe phritz has some "refactor the vm" issues that are relevant

laser [7 hours ago]
I assert to you that we must create an InitActor in order for CreateStorageMiner conform to the specification.

Why [7 hours ago]
I’ll take things I don’t disagree with for $400 Alex

zenground0 [7 hours ago]
Agreement all around. However this is one of those changes that is pretty orthogonal to getting the storage protocol to work and something we can already do. We need to track it but I see it as a secondary priority to (for example) getting faults or arbitrating deals working.

anorth [3 hours ago]
Thanks @zenground0, I concur. Init actor is in our high-level backlog, but I'm not surprised there's no issue yet. Is it reasonable to draw our boundary there for now?

@xiedapao [filecoin mining]
I believe that a solution to this problem is that the rust-fil-proofs CircleCI build needs to be modified to link the libfilecoin_proofs.a archive file to a dummy C program using the same pkg-config file which go-filecoin uses.

@xiedapao it is normal, does not indicate a problem, and there is a PR in review to change from an ERROR to an INFO for the next release: https://github.com/filecoin-project/go-filecoin/pull/2793/files

@xiedapao If you know that these nodes should not be shut down (for example if you yourself are running them, or they are the network bootstrap nodes) then their could be a problem with your node's connection or the miner nodes' connections

@xiedapao This project has come from a protocol labs employee (Alan) who works full time on js-ipfs but essentially volunteered to make this happen.

The safest thing to do, at least in the near term, is think about this as an independent OS project because this work is very loosely associated with day-to-day filecoin project planning. In the long term one of our goals is to support the ecosystem around the core protocol, but we're not there yet as a team.

@xiedapao For question 2: you can either specify the address with --from as an optional argument of miner create or alternatively you can change the wallet.defaultAddress in your config to the address you want to use. That address is the one used by default (if no --from option is passed).

@xiedapao Filecoin is in experimental mode, earlier than beta. The code is open source and you can reuse it under the MIT or Apache 2 license.

@xiedapao error reading identify message: stream reset and failed to send hello handshake to peer are both errors that occur when two nodes using different genesis files try to connect to each other. these can happen normally due to other people on the network connecting incorrectly, but if you're seeing a lot of them, it could mean you're the one using the wrong genesis file.

@xiedapao I think this is a libp2p issue. Sometimes it's had to connect to one filecoin node. it always says "context deadline exceeded", but the node to connect to is definitely online, and could be pinged successfully, of course, port is allowed too. The problem is: sometimes failed, but sometimes succeed to connect. Anyone meet the same issue?

@xiedapao @zenground0: Depending on how badly this impacts devnet useability we may throw in basic time stamp checking with the next release. My opinion: on one hand, this is a good thing, that someone in this network playing as a malicious miner(s), which is a very good test case, will make the network stronger eventually; on the other hand, as you may know, this could be used in marketing promotion from business point of view to mislead investors. So, I do not think this will badly impact devnet useability, however, it might badly impact the ecosystem. It's better to handler this earlier.