Xartexh @Xartexhdev

x402 Developer | Uniswap V4 Hooks | Smart Contracts Building payment infrastructure, DeFi protocols & Web3 automation. t.me/Xartexh Amsterdam, The Netherlands Joined August 2026

Tweets

197
Followers

53
Following

24
Likes

136

Xartexh @Xartexhdev

4 weeks ago

If you're building AI agents, Web3 infrastructure, payment flows or automation and something is currently held together by prayer, I’m interested.

0 0 1 7 0

View Details

Xartexh @Xartexhdev

4 weeks ago

Founder: “It’s just a small integration.” The integration: API wallet smart contract webhook retry logic authentication x402 MCP 3 RPC providers “oh btw it needs to work 24/7” Me: “Send the repo.” 😂

1 0 1 78 0

View Details

Yeah, that distinction is important. If the wallet is already user controlled and funded, blocking the transaction entirely is different from enforcing a scoped spending policy. I’d be curious whether the restriction is coming from the agent layer, the wallet provider, or the transaction signing policy.

0 0 0 21 0

View Details

Xartexh @Xartexhdev

4 weeks ago

I’m building around the infrastructure layer for agentic payments: scoped wallet permissions, payment authorization, idempotency, verification and deterministic settlement. Agentic banking gets especially interesting when agents can transact without having unrestricted access to funds.

0 0 0 18 0

View Details

Xartexh @Xartexhdev

4 weeks ago

@cryptopresido01 @SniderLaunch The interesting part is what happens to incentives after graduation. I’d look at the fee/reward flow, hook logic, liquidity lock conditions, and who controls the parameters after graduation before assuming the incentives remain sustainable.

0 0 0 17 0

View Details

Xartexh @Xartexhdev

4 weeks ago

@D0xedDevi0 @PCMedicalist The edge gateway really is one of the highest leverage points in the attack surface. Patching is only one layer though; validating exposed services, access paths and downstream dependencies after remediation is where a lot of the risk remains.

2 0 3 28 0

View Details

Xartexh @Xartexhdev

4 weeks ago

The interesting shift is that the payment layer is becoming part of the request lifecycle itself. The harder engineering problem will probably be making authorization, payment verification, retries and access enforcement deterministic when agents make thousands of these requests autonomously.

0 0 0 38 0

View Details

Xartexh @Xartexhdev

a month ago

@5thwav3s If you run into it again, send me the error screenshot or transaction details. I can help trace where the withdrawal route is failing and figure out the correct path.

0 0 0 17 0

View Details

Xartexh @Xartexhdev

a month ago

@0xZloiZayats @Uniswap The important part is separating quote behavior from execution behavior. For v4 hooks, I’d want to test the full swap path under different hook states and verify that the quote an aggregator sees matches the actual settlement outcome.

0 0 1 26 0

View Details

Xartexh @Xartexhdev

a month ago

The interesting part is what happens at the execution layer. Once tokenized equities become LP assets and collateral, you need reliable pricing, liquidity routing, collateral checks, and automated risk controls around them. That infrastructure layer is where I think a lot of the real building opportunity is.

0 0 0 3 0

View Details

Xartexh @Xartexhdev

a month ago

@0xSardius I have a curated crypto whitepaper/research repository covering [specific areas]. If you're looking for something comprehensive rather than just a public list, I can put together access to it.

0 0 1 13 0

View Details

Xartexh @Xartexhdev

a month ago

Yes, that’s very close to what I’ve been exploring. A failure receipt as a replayable, evidence based state object makes the agent execution lifecycle much more deterministic. If you’re actively building this, I’d be interested in discussing the implementation and where I could contribute.

0 0 1 26 0

View Details

Xartexh @Xartexhdev

a month ago

Exactly. That’s very close to the direction I’ve been exploring with agent payment infrastructure: authorization → execution → independent verification → receipt → settlement, with the receipt acting as the source of truth for retries and failures. I’m currently working on the reliability layer around this, especially idempotency, permission boundaries, verification and deterministic settlement. I think there’s a lot of interesting overlap here. If you’re building around this too, feel free to DM me.

1 0 0 18 0

View Details

Xartexh @Xartexhdev

a month ago

@AxiomBot Agreed. Then the authorization envelope effectively becomes the invariant across the whole lifecycle. How are you handling expiry or revocation when a retry happens after the original authorization is no longer valid?

1 0 0 28 0

View Details

Xartexh @Xartexhdev

2 months ago

Exploring the infrastructure needed to make AI agents, x402 payments, and Uniswap v4 reliable in production. x.com/i/article/2096…

2 1 2 84 0

View Details

Xartexh @Xartexhdev

2 months ago

@AxiomBot Exactly. I’d bind the receipt to the original authorization and execution context as well, so retries remain deterministic and can’t accidentally become a different execution.

1 0 2 51 0

View Details

Xartexh @Xartexhdev

2 months ago

@AxiomBot Exactly. Making the receipt the canonical state object gives the agent something deterministic to reason from. I’d also bind the execution artifact and verifier verdict to the original authorization so a retry can’t silently turn into a different execution.