Sutoro retweeted
this is getting f*cking dangerous...
REA creator just dropped 20 GitHub repos to build a f*cking reverse engineering studio:
[01] analysis core
> REA: a single MCP that plugs into everything github.com/morluto/rea
> Ghidra: decompiler, free github.com/NationalSecuri…
> GhidraMCP: lets your agent drive Ghidra github.com/LaurieWired/Gh…
> ida-pro-mcp: hooks your agent into IDA Pro github.com/mrexodia/ida-p…
[02] mobile & apps
> jadx: turns Android APKs back into Java github.com/skylot/jadx
> Apktool: take APKs apart and put them back together github.com/iBotPeaches/Ap…
> Frida: hook into apps while they run github.com/frida/frida
> ILSpy: decompiles .NET github.com/icsharpcode/IL…
[03] binary & low-level
> radare2: RE framework that lives in your terminal github.com/radareorg/rada…
> x64dbg: debugger for Windows github.com/x64dbg/x64dbg
> ImHex: hex editor with its own pattern language github.com/WerWolv/ImHex
> angr: symbolic execution engine github.com/angr/angr
[04] network & runtime
> mitmproxy: sits in the middle and reads the traffic github.com/mitmproxy/mitm…
> dnSpy: debug and edit .NET apps github.com/dnSpyEx/dnSpy
> rizin: the radare2 fork github.com/rizinorg/rizin
> raddebugger: the debugger from Epic Games github.com/EpicGames/radd…
[05] rebuild & verify
> awesome-ai-reverse-engineering: 122 repos, every one graded github.com/zhuyansen/awes…
> awesome-reverse-engineering: curated by the guy who made REA github.com/morluto/awesom…
> REA workflows: ready-made investigation prompts, ship with REA
> clean-room loop: SPEC.md, oracles and checks until it matches
how it runs: binary -> REA -> SPEC.md -> rebuild -> oracle -> retry
save this, point it at any app and watch it explain itself.
Sutoro retweeted
Lo biasanya booking hotel lewat Agoda atau Traveloka?
Gue juga dulu gitu. Sampai suatu malam temen gue yang kerja di front office hotel bintang 4 di Bali ngasih satu kalimat yang langsung ngegas otak gue.
Gue tanya: “Kalau gue mau nginep di hotel lo, booking di mana yang paling murah?”
Dia jawab santai:
“Telepon langsung ke hotel. Bilang lo liat harga di Agoda Rp sekian. Minta lebih murah. Kita PASTI kasih.”
Sutoro retweeted
On Nvidia’s Vera CPU –
First, let’s revisit the CPU architecture (see attached image) and its bundled memory
The referenced SOCAMM is a data centre class modular form factor for LPDDR5X (not to be conflated as two different things)
Now, 1 LPDDR5X DRAM die = 9.6Gbps/bit (max). Assuming a 32-bit package, 1 LPDDR5X DRAM package = 9.6 x 32 = 307.2Gbps (~38GB/s) bandwidth
1 SOCAMM is constructed using four LPDDR5X DRAM packages. Total bandwidth per SOCAMM = 38 x 4 = ~154GB/s
The Vera CPU setup uses 8 SOCAMM (8-channel), and therefore has 8 x 154 = ~1.2TB/s of bandwidth
The 1.5TB refers to the capacity. Assuming 32 (8 x 4) LPDDR5X DRAM packages in 1 Vera CPU, this infers the use of 48GB DRAM packages (not 192GB), i.e., 32 x 48. This could be for thermal/power management reasons
In short, each Vera CPU set up = 8 SOCAMMs = 32 LPDDR5X DRAM packages = 1.5TB capacity (32 x 48GB) = up to 1.2TB/s of bandwidth
Second, on market opportunity
Nvidia guided visibility into ~$20B of CPU revenue this year. What is unknown is how this breaks down into sales configurations (and by extension, the memory modules/density types that may be required)
Possible configurations:
1 – as part of Vera Rubin. Assuming NVL72 setup (72 Rubin GPUs, 36 Vera CPUs), total LPDDR5X memory capacity = ~55TB (36 x 8 x 4 x 48), which could potentially be higher if they use higher-capacity memory packages (with liquid cooling)
2 – dedicated Vera CPU racks. Each rack packs 256 Vera CPUs, and therefore up to ~400TB of LPDDR5X memory (256 x 8 x 4 x 48), which could potentially be higher if they use higher-capacity memory packages (with liquid cooling)
3 – individual Vera CPU servers. On the low end will be single and dual socket servers, with one or two Vera CPUs per tray/node respectively. For this configuration, memory capacity = 1.5TB / 3.0TB (assuming use of 48GB modules, with air cooling). Whereas on the high-end, such as the ones being developed by HPE (Cray Supercomputing GX240), this could go up to 640 Vera CPUs = close to ~1000TB. There is also the HGX Rubin NVL8 configuration, with one or two CPUs wired up (with similar memory capacities as a the single/dual socket servers)
In short, it’s challenging to accurately size up the total bit demand for LPDDR5X without knowing the exact sales configurations
What may be a better play is memory PHY/controllers IP –
Each SOCAMM requires 4 x LPDDR5X PHY and memory controllers. For Vera CPU which uses 8 SOCAMMs, each CPU = 32 LPDDR5X PHYs and memory controllers. All that is needed is the average list/sale price for CPU, divide $20B by this number to derive the implied number of Vera CPUs to be sold, that then allows you to derive the dollar content for memory PHY/controllers

























