Meta — Multi-Owner Stacking

Evidence scope: The behavior below is from the pinned Solidity source. A source-file hash does not establish deployed bytecode equivalence. Check the selected deployment and caller before sending a transaction.

MultiOwnable owners have equal authority. The source gate accepts either msg.sender or tx.origin in the owner mapping; adding more owners does not create a multisignature threshold.

The play

Check owner(address) on the exact contract and distinguish token balances, QING staff, bouncers, YUE Origin and direct ownership. Ownership of an intermediary LAU does not automatically make its EOA an owner of every contract the LAU owns. Replay OwnershipUpdate events for enumeration.

The pinned owner() getter returns the contract address. MAP copies the returned address only when its live getter probe succeeds. Check the deployed asset before predicting the QING owner list.

Use these calls here. Simulations preview the current state; each confirmed call is a separate transaction.

QINGResolve your player or venue above the call forms.

QING.owner(address cOwner)Read

Open this function to load its call form.

QING.addOwner(address newOwner)Simulate / call

Open this function to load its call form.

QING.renounceOwnership(address toRemove)Simulate / call

Open this function to load its call form.

QING.setStaff(address _a, bool active)Simulate / call

Open this function to load its call form.

Sources

MultiOwnable, MAP, and QING.