/
Protocol

Contracts

Every address, and what each one can do.

Deployed

ContractAddress
NightFactory0x2b263F8960Ce4f457d156cdA71DB96F671BE9DFe
NightCollection (implementation)0x9Ffe1A9C7391096f304561B8761B8dF1206028AE
NightFactory, second version0x84Fa76c424943b3177B2CBbBB110788689467CaB
NightFactory, first version0xb591d1d2577ae971e64dacf12faff773418d8adc
USDG0x5fc5360D0400a0Fd4f2af552ADD042D716F1d168
NightVerified0x40f9D95E2f745071077c5905a2682aB2f3fcD9da
PonsV2LaunchAndBuy0xe33E9E479dF8802cb0866d5d05258bEc4cF62948
PonsV2LaunchFactory0x7eD598BcEf8bd9Edd8C97A195C6d13f40801EC7e
PonsLaunchFactory, v1, switched off0xA5aAb3F0c6EeadF30Ef1D3Eb997108E976351feB

Why there are two factories

A factory cannot be upgraded: that is the point of it. Adding the token gate and the backing split changed the collection contract, so it needed a new implementation and therefore a new factory. New launches go to the newest; the older one keeps its collections, and both are read. Made on Night means *deployed by a Nightgarden factory*, and that membership is an append-only array on chain with no function that could remove an entry.

What the owner can do

  • Change the fee, within a ceiling compiled into the bytecode. It can come down for everybody; it cannot be raised past the cap to price out somebody who already built here.
  • Pause new launches. This cannot touch a collection that already exists.
  • Name the fee token, once. setNight reverts if it has already been called.

That is the complete list. There is no function that mints, transfers, freezes, or takes money out of any collection.

Next The mark