GatePool: shared broker intelligence
In development: know when a wallet caused chargebacks or fraud at other brokers before it funds an account.
On this page
GatePool in simple terms
GatePool is being built and is not available yet. When it is, brokers that use KYTGate will be able to leave a short, fixed-form signal when a wallet causes them a problem, such as a chargeback after a crypto deposit or confirmed fraud.
When the same wallet later tries to fund an account at another member, that broker will see how many members reported it and why, but never who reported it or anything about the customer.
IN EVERYDAY TERMSThink of shopkeepers on one street warning each other about a forged banknote: they share the serial number, not the name of the person who handed it over.
What it does
GatePool will add one dimension to the screening: whether other members have reported this wallet in the last twelve months, and for what. Reports use a fixed list of event types (chargeback after a crypto deposit, confirmed fraud, an issuer freeze after funding, mule pattern, third-party payment), the chain, the month and an optional amount band. There is no free text.
It will open with public data already in it (issuer freezes, sanctions designations and first-seen dates from the sources KYTGate already reads), so the first member does not join an empty pool.
Why a broker needs it
A wallet that has already burned one broker usually moves on to the next. Each firm sees only its own losses, and the data vendors that see more cannot share one customer's findings with another. A neutral layer between brokers can, under rules every member signs.
How it works
The design, as it stands: wallet addresses are stored as keyed hashes and matched only during a screening. A signal is shown only once at least two different members have reported the wallet, so no single member can mark one alone and no report points back to its sender. Signals expire after twelve months, a member can withdraw its own report, and a wallet holder can dispute a signal by writing to hello@kytgate.com.
A pool signal will never decide on its own: under the default policy it sends the event to human review, and anything stricter is a choice the member makes in its own policy. Every report and every lookup will be written to the audit log.
No member report will be accepted until a data-sharing agreement and a data protection impact assessment are in place.
What it does not do
GatePool is not available today and nothing on this page is a live feature. When it ships it will not share which member reported a wallet, customer names, e-mails, identities, exact amounts or free text. It will not reject funds on its own, and it will not replace sanctions screening or your own due diligence.