One Bitrue Tag, Ten Projects
A reader asked whether one Bitrue deposit tag, shared by eleven wallets, meant those wallets were one person. They are not. The tag is Bitrue's intake for listing and launchpool supply — two deposits match Bitrue's announced reward pools to the exact token amount, one of them the day before Bitrue posted it — and the wallets sharing it are unrelated projects Bitrue was listing.
The tell: deposits that matched Bitrue's own numbers
The wallet r3RaNVLvWj… is labelled “Bitrue Tokens” (bitrue.com) — the address Bitrue uses to receive token deposits. On the XRPL you separate one deposit from another with a destination tag, a number on the payment. On tag 812314804, 2deposits give the game away: they equal Bitrue's announced reward pools to the token.
On 2 December 2024 a wallet sent exactly 194,000 RPLS to the tag. The next day Bitrue announced the RPLS launchpool — “stake $BTR to share 194,000 $RPLS”. The supply was in place a day before the pool was public. And on 14 November 2024 a wallet sent 1,250 DROP— the exact size of Bitrue's announced DROP vote-reward pool. A retail customer does not hold next-day launchpool figures; the exchange running the pool does.
Four listings, one tag
These deposits into the tag line up with Bitrue's own listing posts — click each source to check:
| Token in | Amount | Deposited | Bitrue listing / pool | Tx |
|---|---|---|---|---|
| BERT | 3,500,000 + 2,000,000 | 5–6 Nov 2024 | Listed 5 Nov, withdrawals 6 Nov 2024 | 99DF28E1… |
| DROP | 1,250 + 1,249 | 14 Nov 2024 | Vote reward pool = 1,250 DROPexact | 987C7D73… |
| RPLS | 194,000 | 2 Dec 2024 | Launchpool = 194,000 RPLS (posted 3 Dec)exact | 593930C1… |
| PHNIX | 280,000,000 | 7 Jan 2025 | Listed 7 Jan; Launchpool 9–12 Jan = 186,000,000 | 20C769BF… |
These four are the ones cross-checked against Bitrue's posts. The same tag has 11 payer wallets in all and nine tokens traced — among them 98,000,000 FUZZY (AF05DC10…, 2 Nov 2025) and 2,199,000 aixrp — spread across a full year. This is a standing operations address, not a one-off.
Why it cannot be one customer
Bitrue does give each customer their own tag: of this wallet's 7,892 tags, 6,979 (88%) have exactly one payer. Tag 812314804 is a rare exception, with 11.
And those 11are not one person's wallets. Every XRPL account is created by another that first funds it — its activator, a permanent first record. These payers have 10 different activators, and none funds another. Ten independent origins, each sending its own separate token that Bitrue then listed: that is ten projects routed through one exchange address, not one operator with ten wallets.
What a shared tag proves — and what it doesn't
A shared deposit tag fits two different stories — one owner with many wallets, and many owners using one exchange — so on its own it proves neither. Here the tie-break is decisive: the deposits equal Bitrue's own launchpool figures, so the account is the exchange's, and the tokens sharing it are simply the ones Bitrue listed.
This is why xrpl.to treats a shared exchange deposit tag as the weakest signal and keeps it apart from the strong ones. On a token page, a connection resting only on a shared tag is now marked tag-only and counted separately from links backed by a shared wallet, a shared signing key, or the funding chain — evidence only the same controller can produce. The tokens above share this tag and nothing else, so none is evidence that the others have the same owner.
Verify it yourself
Open any transaction above — each is a payment from a different wallet to the same Bitrue address (r3RaNVLvWj…) and the same tag (812314804). Then read Bitrue's own RPLS launchpool post: 194,000 in, 194,000 announced. Nothing here needs to be taken on trust. More in other insights.