The Alexandria Protocol, independent technical and usability review
We reviewed the Alexandria Protocol from 7 to 16 October 2026. The findings below are as of 12 October 2026, observed independently by PulseHawk and published with the client's consent. What we checked ourselves stays apart from what the team reports about its progress since.
The review in short
- Reviewed
- 7 to 16 October 2026
- technical and usability review
- Findings as of
- 12 October 2026
- each finding below carries this date
- Published
- with the client's consent
- consent given on 1 November 2026
- Anchoring of AP-0031
- not anchored
- as of 4 November 2026, see the last section
What did we review?
We worked from four sources.
- The reviewer brief from the Alexandria team, with the hashes it names for AP-0030 and AP-0031.
- The two records AP-0030 and AP-0031.
- The public walkthrough video of 10 October 2026.
- The public app, which we used on 12 October 2026.
The project page of the Alexandria Protocol is the-alexandria-protocol.replit.app.
What did we confirm on 12 October 2026?
- Downloads match the brief. AP-0030 and AP-0031, downloaded on 12 October 2026, matched the hashes in the reviewer brief byte for byte.
- Hashing stays on the device. The app hashes a file locally in the browser, and the file does not leave the device. Checked 12 October 2026.
- New versions are clean. A new version creates v2 cleanly, and v1 stays unchanged. Checked 12 October 2026.
- No fork at the same place. A second version at the same place is blocked, so a record does not fork. Checked 12 October 2026.
Checked by PulseHawk on 12 October 2026, in the public app and with the files we downloaded that day.
What was still open on 12 October 2026?
- Same file, new title. The same file with a different title was accepted as a new original entry, without a warning. Observed 12 October 2026.
- The operator is the trust anchor. Until a record is anchored, trust rests with the operator of the service. Observed 12 October 2026.
- ALX-KASPA-1 is not specified in public. There was no published specification and no test vector for ALX-KASPA-1. Observed 12 October 2026.
- Anchoring for entries of others. The app offered to anchor entries that other people had created. Observed 12 October 2026.
- Archive standards and a second store. The archive standards followed and a second storage location were not named. Observed 12 October 2026.
Observed by PulseHawk on 12 October 2026. Points the team may have changed since are not checked again on this page.
How far has the project come, according to the team?
On 1 November 2026 Kas Knight told us, for the Alexandria team, that a first anchoring path on Kaspa Testnet 10 (TN10) had been tested. Since 1 November 2026, 21:24 UTC, an anchoring transaction for study 52 is on TN10.
Statement of the Alexandria team, 1 November 2026. The anchoring transaction is checked below.
What did we check on the anchoring transaction?
Checked by PulseHawk on 2 November 2026, on two public TN10 nodes, read only. Every value in this list is counted.
- Transaction accepted. Transaction
3db50bc618db869ebfdda76381d7d5beb491f61a97426faadd02d831dfd70269is on TN10 and accepted in block9afd242166b4ddc2b900b30c6d6016014414c2dd199d7856804213bf0618a7d5, on both nodes. - Block time. The accepting block has the time 1 November 2026, 21:24:24 UTC.
- Payload. The payload matches the expected text byte for byte, 85 bytes.
Still open on 2 November 2026.
- Input and fee. The input, and with it the fee, could not be read, because the transaction before it is older than what both nodes keep.
- Commitment. The commitment in the payload cannot be computed again without a published ALX-KASPA-1 specification.
Counted by PulseHawk on 2 November 2026. No addresses are shown on this page.
Is AP-0031 anchored?
No. As of 4 November 2026, the date of this page, AP-0031 is not anchored. The transaction checked above anchors study 52. Until a record is anchored, trust in it rests with the operator.