seaport VS aavegotchi-contracts

Discussion forum for Seaport

Repo: https://github.com/ProjectOpenSea/seaport/tree/1.2

1 Opensea seaport Conduit https://github.com/ProjectOpenSea/seaport/blob/main/contracts/conduit/Conduit.sol

Not yet. But the core protocol seaport protocol is open ( https://github.com/ProjectOpenSea/seaport ). The system it self is not stable so if you want the most you can do is test it out at https://decentool.com/checkout ( don't use it on main net instead use Mumbai network because the system is a little bit unstable ). I am planning to make it open source once the system is stable and secure

Here's the seaport protocol github: https://github.com/ProjectOpenSea/seaport

I'm talking about procedurally generated tokens from seeds rather than statically stored. See the Aavegotchi repo and look at the storage and SVG generation contracts if you want to.

The AavegotchiDiamond has many upgrade scripts. Check them out for more code examples.

The smart contracts address This is essentially the URL of the target smart contract, we can find what this is by going on the Aavegotchi Contracts GitHub for the contracts. We want the Aavegotchi diamond address as it has access to all the facets we need.

Checkout Aavegotchi's libraries which are used across facets.