mirror of
https://github.com/pezkuwichain/pwap.git
synced 2026-07-28 01:05:40 +00:00
pezkuwichain
dd58fe9164
- calculateMultisigAddress was completely broken (hex-decoded an SS58 string and never hashed the preimage) - fixed via @pezkuwi/util-crypto's real encodeMultiAddress/createKeyMulti, verified against the actual known multisig address on-chain. - ReservesDashboardPage had stale Noter/Berdevk addresses that don't match the real signers - centralized as BRIDGE_MULTISIG_SPECIFIC_ADDRESSES. - USDTBridge withdrawal called assets.burn directly as a single-signer extrinsic (always fails - only the multisig is Admin) while only checking status.isFinalized (a failed dispatch is still finalized, so it silently did nothing) - replaced with the correct transfer-to-custody flow the relayer actually watches for. - New MultisigOperationsPage (/multisig/pending) lists pending calls from real Multisig.Multisigs storage and lets any of the 5 signers approve/reject with their own wallet extension. - New standalone sign/ app (deployed separately at pezbridge-sign.pex.mom) - a dedicated, gated signing portal for the same operations, so signing isn't dependent on this app alone.
17 lines
678 B
TypeScript
17 lines
678 B
TypeScript
import { BRIDGE_MULTISIG_SPECIFIC_ADDRESSES } from '@pezkuwi/lib/multisig';
|
|
|
|
export interface SignerSet {
|
|
name: string;
|
|
specificAddresses: Record<string, string>;
|
|
}
|
|
|
|
/**
|
|
* Every known multisig this site gates access for. The connected wallet is authorized if it's
|
|
* a member of ANY set below - add new entries here as new signing needs come up (this is the
|
|
* single registry the login gate checks against, per the design decision to keep one dedicated
|
|
* portal for all future signing needs rather than a bespoke UI per multisig).
|
|
*/
|
|
export const SIGNER_SETS: SignerSet[] = [
|
|
{ name: 'USDT Bridge Treasury', specificAddresses: BRIDGE_MULTISIG_SPECIFIC_ADDRESSES },
|
|
];
|