Remote procedure call

The first checkpoint is network data.

Ark runs on chain ID five thousand and forty-two with the RPC endpoint at rpc.mainnet.ark.io. Wallets may still display the gas balance as, quote, "ETH eighth" unless they've added custom support for USDC as gas.

Advisors need to confirm these parameters in their custody systems before initiating any transfers.

And what about the fee structure? How does pricing work when USDC is the gas token?

If you clear an address to zero, you can't send any further outbound transactions.

Also, at measurement time, on September sixteenth at zero three fifty-seven UTC, the public block explorer at explorer.arc.io redirected to a Cloudflare access sign-in.

If the explorer is unavailable, advisors should query the RPC directly for transaction verification.

Don't rely solely on web interfaces.

... maybe aren't familiar with that term?

When you're, when you connect with a server, when you type in, um, like something on a, uh, a browser, or you make an RPC call, you talk to some physical server.

And, um, actually, you probably talk through 20 to 50 different physical machines all in that, uh, short amount of time, switches and...

But something terminates that connection, and what you end up talking to, what you authenticate to, that would be, that would, you'd say that's the edge of a network.

And then the origin server, whatever is actually providing the content, may be anywhere in the world, but Cloudflare makes that, um, safe for the origin server, but fast and performant for you as a user.

Um, I really appreciate the business model because you're selling a actual service, and it's beneficial for the customers and, like, your customers and the people who are using, um, the service.

And so at, at Helius, we have a very similar, um, model where it's really beneficial for the people who are using us, and it's beneficial for Solana and, and the network to have this access layer being an RPC provider, but also, um, helping participate in the network itself through validator operations.

So edge, edge network is all of the infrastructure that people would connect to, um, that then decides how to respond to requests.

ALPC, they write, is the foundational interprocess communication mechanism in Windows.

It underpins RPC, COM, and a broad set of system services, and is present and active on every supported Windows version from workstation to server core.

Because ALPC operates at such a low level in the kernel's IPC, interprocess communication path, vulnerabilities here tend to be reliable privilege escalation primitives once an attacker has any local code execution.

This class of flaw has historically appeared, s- and they're, they're repeating themselves, in post-compromise tooling used by both commodity malware and targeted intrusion operators as a reliable final step from user mode to kernel mode control.

You could do little Bobby tables.

If you have RPC access to a server that's running wallets already.

So I guess if you're running an Uncle Joe setup where people can create their own Bitcoin Core wallets on your Bitcoin Core node that you have given them VPN access to or something, they could break out of it.

I think Uncle Joe is usually Stalin.

LND, this is a change so that LND will now always say explicitly which channel type it wants when opening a channel, which is actually what the spec requires.

It puts the channel type in the open channel and then spits it back out in accept channel, and then it also rejects incoming opens that leave out that field.

So maybe one thing to note here is that if you're using LND and you open a channel through the RPC without picking a type, LND picks one based on what it thinks both sides, well, what it knows both sides support.

And this is sort of tied into the fix that we talked about back in newsletter 4.7 where LND was picking a taproot channel implicitly and then failing on it.

I'm, I'm using, like, a privacy protocol, so I- I'm private now." And it's like, well, no, um, because, uh, you didn't use a VPN or Tor or anything, and, um, it's very public.

Um, or, like, you, your wallet had, like, RPC codes, uh, to ask for some states you needed to build a transaction, and that actually reveals, uh, the state you, you needed to build the s- the transaction, so it leaks your privacy as well.

So yeah, for me, it's really about, like, trying to, to think comprehensively of like what a full privacy experience looks like.

Um, and then the next step is to make it completely invisible to the user.

The, the, the first is, um, uh, network metadata or IP addresses and everything that are just, uh, completely transparent if you don't, uh, yourself use Tor or VPN or sort of, like, custom way, so...

And we want this to be embedded in the wallet so, like, users don't have to think about it.

Um, and then there is an- another thing where your wallet calls RPC, uh, providers to ask for state to build transactions, and that also leaks what exactly, what piece of state you need to build your transaction, which reveals your intent and, and sort of like what, what you want to do, uh, about the, the transaction And then, you know, the, the other important part, so I talked a lot about the protocol, but, like, the, the less important part is, like, the privacy app itself, right? Um, also it, it, it can't leak.

Um, I think there are some properties I really like, uh, that not all privacy apps, uh, have.

ALPC, they write, is the foundational inter-process communication mechanism in Windows.

It underpins RPC, COM, and a broad set of system services and is present and active on every supported Windows version from workstation to server core.

Because ALPC operates at such a low level in the kernel's IPC, inter-process communication path, vulnerabilities here tend to be reliable privilege escalation primitives once an attacker has any local code execution.

This class of flaw has historically appeared, and they're repeating themselves, in post-compromise tooling used by both commodity malware and targeted intrusion operators as a reliable final step from user mode to kernel mode control it's amazing there's a term called commodity malware commodity yes off the shelf yeah you know just your regular off the shelf that's right would you like this one