Great post related the recent attacks on Monero! The BEAM community is so smart and I love it.
Afaik, this is how Beam handles checkpoints:
Beam is full PoW, with an algo that allows ASICs but without then having too much of an advantage over GPUs.
The blockchain is lightweight, so every wallet seamlessly runs its own node.
Regarding reorgs, Beam produces one block per minute in average, with automatic rolling checkpoints every 60 blocks (1 hour).
Nodes of course automatically follow the longest chain, but won’t go with reorgs deeper than 60 blocks (except for one case: if no new blocks are produced on the branch for more than one hour).
Thats why CEXs, by instance, request 60 confirmations for deposits (withdrawals are done in one minute, because they don’t put the CEX at risk in case of reorg).
In fact, nodes can still accept deeper reorgs, up to 1440 blocks (one day), but that can only be enforced manually. That’s the "hard" finality.
With all that, if an attacker tries to reorg deeper than one hour, no nodes will follow its chain, even if it’s longer, as long as honest nodes keep producing blocks on the honest chain.
The idea is that the attacker will stop its attack when it sees it doesn’t really work.
In other words, as long as the network is alive, and honest miners produce blocks, there is no problem. All the nodes will just ignore the attacker's blocks.
The system is not perfect though, because newcomers, who have not sync’ed their node in a long time, might follow the attacker’s chain (as they’ll follow the longest, without having the history of the reorg). Adding some “trusted” peers in the wallet config could help in that case.
Also, to avoid network fragmentation into disconnected clusters, some nodes have organized in "persistent" peers, ensuring interconnections between them.
The system is not an absolute protection against 51% attacks, but I understand this system has protected Beam quite well from multiple attacks since it was implemented.
And it remains 100% PoW.