wwhchung

Confirmed that this is still an issue. disconnect events are erroneously being emitted when chain switch happens. In our case, because we respect this event, we disconnect an authenticated account.

This isn’t a published npm package. This repo is intended to be a reference for others rather as a direct dependency.

I've been able to resolve this by doing the following: 1. Add 'timeout' param to the RPC call. Example: {"jsonrpc":"2.0", "method":"^Cbug_traceTransaction", "params":["0xa97067dd04cf7ab72a11c56af7506e16b0b70a6b0131840c7221e1aad05ba753", {"timeout":"120s", "tracer": "callTracer"}], "id":1} 2. Configure the node...

Opensea does not rely on owner or OwnershipTransferred because it’s easily spoofable.

> Event easily spoofable for sure, owner is what the contract considers owner. Yup, but OpenSea typically doesn't use this to group things under an address's 'created tokens' because that...

> Well, if I'm the owner of the contract, it makes sense that the items were created by me... Not necessarily. I could create a contract with a fake owner...

I had tried that (CL and Erigon stopped) and still encountered this error.

How do you get this output info? > Just an update on the above, the snapshot stage eventually kicked in and caught up: > > ``` > stage_at prune_at >...

> Did you wait for Erigon to fully settle down? I waited for it to complete the snapshot phase, which took over a day. That did it. Thanks. Upgrade successful.

> @wwhchung thought, does maxPerWallet limit need to be enforced anywhere here? that's my only reserve atm, contract looks perfect besides that. No, because server enforces properly and the 'same'...