Add endorsements contract to devnet

[rvagg]

Done Criteria

Minimum:

• Deploy contract https://github.com/FilOzone/filecoin-services/blob/main/service_contracts/src/ProviderIdSet.sol
• Record contract address in contracts.json

Bonus:

• Enable configuration file that lists SPs to add to the the contract. (If there is no first-class support, it's still possible for someone to unblock themself by calling addProviderId
• In "how to use with Synapse example documentation" (Example of how to use with Synapse #7), show setting ENDORSED_PROVIDERS_ADDRESS (or whatever it gets called) as env var to https://github.com/FilOzone/synapse-sdk/blob/master/utils/example-storage-e2e.js like the other contracts

Why Important

Synapse by default as part of https://github.com/FilOzone/filecoin-services/issues/357is going to use multiple SPs/datasets when creating a dataset and adding pieces, and one of those SPs needs to be an "endorsed" SP as specified in the "endorsements contract". We want the default devnet to work for the default synapse setup.

Notes

1. This is in support of [Project] GA durability (2 copies; 1 with endorsed SP) filecoin-services#357

[wjmelements]

parse_deployment_output gets the contract addresses from the output text. I think a better approach would be to read them from deployments.json.

[rvagg]

Yeah, sorry, deployments.json is what I meant. I banged this issue out late at night on my phone while it was top of mind.

[rvagg]

Actually. Maybe I'm not following the suggestion here. You mean deployments.json from filecoin-services on running the deploy script I guess? I'm not too fussed about how it gets read into the system, more about how it gets made available outside of the system. So whatever's consistent.

[wjmelements]

Prefer to discuss that in its issue
#42

[rvagg]

OK, back at the computer now. To clarify, this is the workflow that should work after this, with the new address injected into it:

jq -r '.run_id' ~/.foc-devnet/state/current_runid.json

cd synapse-sdk
PRIVATE_KEY=0x$(jq -r '.[] | select(.name=="USER_1") | .private_key' ~/.foc-devnet/keys/addresses.json) \
RPC_URL=http://localhost:5701/rpc/v1 \
WARM_STORAGE_ADDRESS=$(jq -r '.foc_contracts.filecoin_warm_storage_service_proxy' ~/.foc-devnet/state/latest/contract_addresses.json) \
MULTICALL3_ADDRESS=$(jq -r '.contracts.multicall' ~/.foc-devnet/state/latest/contract_addresses.json) \
USDFC_ADDRESS=$(jq -r '.contracts.usdfc' ~/.foc-devnet/state/latest/contract_addresses.json) \
node utils/example-storage-e2e.js <file>

It was ~/.foc-devnet/state/latest/contract_addresses.json that I meant in my original issue description. How we get there is another matter to be figured out between you and @redpanda-f, but the outcome here should be that the new address shows up and can be accessed externally.

[BigLep]

I have flushed out the done criteria a bit and added more context.

@wjmelements : I see you're assigned to this currently. No pressure, but are you taking this on?

@rvagg : FYI that I have added this to FilOzone/filecoin-services#357

[wjmelements]

I have begun work on branch wjmelements/endorsements-address