Rüdiger Birkner

Research Scientist @DFINITY |

[DFINITY Foundation @dfinity]

SEV Subnets are now live on the Internet Computer.

We sat down with Björn Tackmann to understand what they actually are and why they matter.

He starts with the problem: standard cloud infrastructure writes your data to memory in plaintext. Anyone with access to the hardware can read it. That's not a flaw in any specific product. It's how computers work.

SEV Subnets are the Internet Computer's answer to that. Full conversation below.

[Rüdiger Birkner @r_birkner]

@icpindex @dfinity @PierreSamaties @bjoerntm Hey, this is Rüdiger from the Boundary Node team. Sorry about that hiccup, it was an issue on our side and is resolved now. Thanks for reporting!

[bjoern.icp ∞ @bjoerntm]

Proposal 140407 creates the first subnet consisting entirely of nodes that support SEV-SNP. Smart contracts on this subnet will be able to keep their state and computation fully confidential! 🔒
https://t.co/n4uiQh0DIU

[dom | icp @dominic_w]

Important Privacy News: some Internet Computer (ICP) nodes have started leveraging special privacy hardware on the node machines (SEV-SNP/TEE tech).

Whats cool — even if someone gains *physical access* to these node machines, they will only find encrypted bytes inside.

[Rüdiger Birkner @r_birkner]

@Zforever97 @devdaryl @973H2B @caffeineai @dehypokriet @CanessaEmilio Hey @Zforever97, can you please reach out such that we can look into the specific issues you are experiencing.

[DFINITY Foundation @dfinity]

A new level of transparency has arrived on the Internet Computer. 🔎

For the first time, API boundary node access logs are publicly available in real-time.

Now you can:
🔎 Get fine-grained insights into canister usage, including queries.
📊 Track activity across popular dapps and the overall network.
➡️ Stream access logs directly from ICP.

Get the full details in our blog: https://t.co/DnMWVMF8ir

[Steve @stevekimoi]

Hey ICP devs — quick tip 💡

Need to point your custom domain to a canister ID without the hassle?

Check out CanisterDNS → https://t.co/1nGIcozTDe

Just drop in your domain + canister ID, and it spits out the exact DNS config you need and the necessary steps.

Takes seconds. No guesswork. No digging through docs.

Bonus: Works for subdomains too!

[Rüdiger Birkner @r_birkner]

@JesseThaGreat_ @coinNationHQ Your assumption is correct: One of the API boundary nodes in Atlanta is experiencing issues. The HTTP gateways did not stop routing requests to it. This has been fixed. See here: https://t.co/VHVzGXNzqU

[Rüdiger Birkner @r_birkner]

@coinNationHQ Sorry for the issues! Here is what happened: The API boundary node in the at2 DC had no IPv6 connectivity. Hence, it was happily responding on IPv4, but could not talk to any other machine on the IC as it is IPv6-only.

[Rüdiger Birkner @r_birkner]

@coinNationHQ Only 1 out of the 20 API BNs had that issue. Since HTTP gateways use proximity-based routing some regions routed more requests through that API BN (mostly the US East Coast). However, when loading a frontend, it doesn't help that most requests succeed if a critical one fails.

[Rüdiger Birkner @r_birkner]

@coinNationHQ Sorry for the issues! Here is what happened: The API boundary node in the at2 DC had no IPv6 connectivity. Hence, it was happily responding on IPv4, but could not talk to any other machine on the IC as it is IPv6-only.

[DFINITY Foundation @dfinity]

With the latest Solenoid Milestone, ICP’s boundary nodes are now fully decentralized.

Watch Nikolay Komarevskiy & @r_birkner demo ICP’s decentralized edge architecture and routing requests through the API boundary nodes 👇

https://t.co/qGZ8raPt7v

[DFINITY Foundation @dfinity]

ICP just leveled up with the Solenoid Milestone.

Boundary nodes—the mailmen of the IC 📫 —are now fully decentralized.

What's New?

🔹 API Boundary Nodes: The public edge, routing requests with precision
🔹 HTTP Gateways: Enable direct browser access to canisters
🔹 Discovery Library: Tools for direct API boundary node access

https://t.co/PKBaPMQhSu

[Rüdiger Birkner @r_birkner]

@Zforever97 @bobdotfun @BobonBobicp This is an issue on the boundary nodes and not a problem of the Bob canister itself. We are working on resolving it.

[DFINITY Developers ∞ @DFINITYDev]

🔦 Individual Spotlight: Boundary Node team lead 🔦

This week, we sat down with @r_birkner to chat about:

🔶 #Boundary #node architecture updates.
🔶 Challenges as a team lead.
🔶 Upcoming Tokamak milestone.

Read the full interview: https://t.co/UmKETAGkML

[DFINITY Foundation @dfinity]

Don't let FOMO kick in - relive the best moments from yesterday's #ICP 3rd Anniversary celebration here.

Community members and partners joined us at DFINITY HQ for keynotes, panels, and an epic party.

Catch up on some of the highlights here👇

[jan @JanCamenisch]

To #icp! 🍷

[David Dal Busco @daviddalbusco]

Check it out, @nathanosdev is releasing the HTTP certification library for #Rust! 🦀🥳

This crate enables you to build an #icp asset canister that supports fancy features like custom 404 pages while remaining secure!

https://t.co/Ix5kkNAwRI

[Rüdiger Birkner @r_birkner]

@lukasvozda @sonic_ooo @ICPCoins The first inscriptions brought the boundary nodes to capacity. In hindsight, this was great as it uncovered inefficiencies in the services. Now, the BNs can handle way bigger loads and several events (e.g., Ghost inscriptions) happened without any hiccups.

[Rüdiger Birkner @r_birkner]

@lukasvozda @sonic_ooo @ICPCoins The two dapps are hosted on different subnets. So, I doubt that it was the subnet. Most likely, it has to be some undetected boundary node issue, or something to do with your setup.

[Rüdiger Birkner @r_birkner]

@lukasvozda @sonic_ooo @ICPCoins For further investigation or in case experience similar issues again, it would be great if you could share more details with us (via PM or on the forum): where are you connecting from, what are the symptoms (e.g., connection fails, status codes).

[Rüdiger Birkner @r_birkner]

@lukasvozda @sonic_ooo @ICPCoins Hey @lukasvozda, Boundary Node Team here. Sorry to hear that there were issues during yesterday's airdrop. We had some issues before, but for yesterday, I don't see anything on our end: metrics and logs look good, no machines was even close to capacity, no alerts went off.