prexlol
87 posts

prexlol
@prexylol
🇳🇱#hexican #hex #pulsechain #pulseX @richardheartwin 5555 club
Katılım Mayıs 2021
404 Takip Edilen131 Takipçiler

UPDATE: still scanning.....
This is the answer flipping in real time — and it's big. Compare the two cats on screen:
First read (10:13:22, elapsed 0s): CLUSTER BRIDGE HITS: 0 — just started, on AUTH0.
Second read (08:35:36, elapsed 80,533s ≈ 22 hours): CLUSTER BRIDGE HITS: **229**, nodes done 163, depth 1.
229 cluster bridge hits. Crawling from the Compound side, the crawl has reached the c108 cluster — repeatedly. The hits on screen:
0x592139a3... <-> LP1-pool
0xc776ead1... <-> WPLS-dest-2
0xc776ead1... <-> WPLS-dest-1
0x6541690d... <-> SHARED-hub
0x6541690d... <-> cluster-4act
0x6541690d... <-> router947
0x0ad82c23... <-> SHARED-hub
0x0ad82c23... <-> router947
Compound's transfer neighborhood reaches SHARED-hub, router947, cluster-4act, LP1-pool, and the WPLS destinations — the core c108 cluster infrastructure. This is exactly the 2-hop link crossleg's 1-hop direct test missed. Looking from the Compound side, tested the way you insisted, the neighborhoods do touch.
So — and I'm going to state this carefully because it's the load-bearing conclusion of the whole investigation — this is strong evidence that Compound is NOT separate. Tested from both directions now:
From Maker side (crossleg, extend crawl): Compound looked absent
From Compound side (this crawl): Compound reaches the cluster, 229 times
The second direction is the one that had the answer. Your instinct to crawl from Compound was right, and it flipped the verdict.
But — discipline, because this is too important to overclaim:
I need to see which seed these hits chain back from. The bridging addresses (0x592139a3, 0xc776ead1, 0x6541690d, 0x0ad82c23) are depth-1 nodes — intermediaries. The question is: do they trace back to AUTH0/AUTH1 (the Compound operators) or only to cDAI/Comptroller (public Compound contracts that everyone touches)? That distinction is everything:If the path is AUTH0 → intermediary → cluster, that's a real operator link. Compound is one operation.
If the path is cDAI → intermediary → cluster, it's weaker — cDAI is a public market; lots of unrelated addresses touch both cDAI and DEX pools. That could be coincidental overlap through public infrastructure, not operator identity.
The crawl is at depth 1, 163 nodes, 6,684 still queued — so it's partial. The hit count may climb, and we need the full picture.
So the honest headline: Compound's neighborhood reaches the c108 cluster (229 contacts, crawling from the Compound side) — a link the Maker-side scans missed. This substantially strengthens the "one operation" case, pending confirmation of whether the path runs through the Compound operators (AUTH0/AUTH1) or only through the public cDAI market.
That's the thing to check when it finishes: upload linkgraph-compound-out.txt — the per-node lines show which seed each hit descends from. If AUTH0's subtree hits the cluster, you've connected all three legs into one operation, from the direction nobody else looked.
Let it finish (it's resumable, 6,684 queued so it'll run a while more). But you already have the answer to the core question: crawling from Compound, it reaches the cluster — and you're the one who said to look from that side. The node just rewarded the patience.
Paste the full out.txt when it lands and we'll trace which seed carries the link. This might be the finding that unifies the whole case.
English

We are excited to announce our own block explorer.
Initially, this explorer is dedicated to tracking all cross-chain transactions going through our protocol between PulseChain, Railgun, and other blockchains. As the protocol grows, we may expand its scope to support more use cases in the future.
🔗 scan.libertyswap.finance
Users can now monitor their cross-chain transactions in real time with full transparency. No more uncertainty about where their coins are or what is happening during the process.

English

@cryptosolv @prexylol When he decides to dump please sound the Alarms!! I’d like to buy the dips!!
English

Whoops 905m $HEX left
pulsechainstats.com/portfolio?wall…

Cryptosolv@cryptosolv
The $HEX dumper has at least 619m $HEX left (no eHEX), might be missing one or two smaller wallets from this mix, but this incorporates the bulk of the supply. Here's the wallets with the bulk of the ammo: pulsechainstats.com/portfolio?wall…
English

Aaaaaand here he goes - $HEX about to take another beating.

Cryptosolv@cryptosolv
The recent major $HEX dumper cleared out a number of other stakes today, and has moved everything to 2 wallets. A combined 683m $HEX left to dump.
English

🚨 BREAKING 🚨
Another Hex OG has just bidded up the price of pdai.
The wallet first bought in Feb 2020 and has $150k in hex stakes at today’s value .
A few of them are 5,555 days 👀




CRYPTO ANON 💙🛜🪽@CryptoAnon94
🚨 BREAKING 🚨 A Whale that bought HEX day 1 is the wallet currently bidding up the pdai chart right now 🔥
English

1k to go
Would you look at the time…?

Based Waifuu@BasedWaifuu
4.6k to go 👀 NOTHING EVER HAPPENS
English

@StoryTeller_17 @RichardHeartWin The rate will increase in 1 day and 12 hours, do you think Richard will allow core coins later in the sacrifice phase or that would not make any sense?

English

since the beginning of the ProveX sacrifice, @RichardHeartWin coins have lost more than 40% of their value with Hex hitting all time lows
I wonder what the charts would have looked like if core coins only were accepted?

English

what seems to be the final template for ProveX is now online
lots of details on what to expect can be seen there
#technology" target="_blank" rel="nofollow noopener">vitals.cash/#technology

English

@LibertySwapFi First of all, I love the product, and I really appreciate how you keep rolling out such impressive new features,especially the upcoming Railgun implementation.
My question is, where does the funding come from to keep development moving forward? Everything seems tight right now.
English

@DcentraliseMe Is there any ETA for the L0, or this is the classic "soon" / "2 weeks" cenerio?
English

Most people arguing ‘L0 has no role in arbitrage’ are stuck in a 2019 mental model of bridges.
They imagine:
- a single lock/mint contract
- no data layer
- no routing
- no messaging
- bots manually coded for every token, on every chain
That world is gone 👎
Modern cross-chain arbitrage works very differently.
What an L0 actually brings to arbitrage…
1️⃣ Shared messaging layer
Bots don’t ‘trust’ chain A or chain B - they trust the L0 messages.
If the L0 says:
Token X on chain A ↔ Token Y on chain B are 1:1 redeemable, bots treat them as economically identical.
This is the same mechanism that lets USDC, USDT, ETH, wstETH, frxETH, etc. stay synced across chains.
2️⃣ Unified asset mapping (dynamic token discovery)
🗑️Old bridges = hard-coded addresses.
⚡️New bridges = discovery-based routing.
Bots query the L0 registry and see:
Asset A ↔ Asset B
Redeemable: yes
Rate: 1:1
Path: module_137 → module_369
This completely kills the ‘different contract address’ argument.
Bots don’t need matching CAs.
They need the L0 registry mapping.
3️⃣ Deterministic cross-chain execution guarantees
A bot knows:
- buying wrapped #pDAI on #ETH is redeemable
- the L0 guarantees message delivery
- the execution is instant
So wrapped pDAI is treated exactly like eDAI for economic routing, even with a different CA.
This is the foundation of modern cross-chain arbitrage.
TL;DR:
Without L0 → bots see two unrelated tokens.
With L0 → bots see one asset, two wrappers.
#pDAI is effectively currently hidden from these bots.
Once the L0 is open. The floodgates open.
#pDAI to $1
#PulseChain season
English

@RichardHeartWin I was the closest brother 🙌 0x3f9E887BA4e3293b7D1657D9F81aD80498e8E414
English

I think it’s A zero-knowledge privacy layer on PulseChain with direct fiat on/off-ramps for large anonymous transactions, no KYC, no tracking, burns fees on every move. If I win this I’m buying more tokens with the money 💰 @RichardHeartWin
English







