Return all $3.8M — that’s already good. But what caught my attention here is something else.
The responsible party was identified within 24 hours. And that really changes the story itself: the infrastructure problem remained a local incident rather than turning into a blow to trust in the protocol.
It’s also important to note that the $NEAR Protocol network, as stated, is not related to this incident.
But it’s exactly at the intersection of different systems where I would keep looking for weak spots. That’s where the most confident assumptions about security often break.
The responsible party was identified within 24 hours. And that really changes the story itself: the infrastructure problem remained a local incident rather than turning into a blow to trust in the protocol.
It’s also important to note that the $NEAR Protocol network, as stated, is not related to this incident.
But it’s exactly at the intersection of different systems where I would keep looking for weak spots. That’s where the most confident assumptions about security often break.