Why RCF > other code protections

Posted by rcf-protocol on Thursday April 23, 2026 @09:13AM
from the self-post dept.

Obfuscation gets broken by AI. Watermarking is too late. Licenses get ignored.

RCF: Visible for humans + technical barriers + legal line "Visibility ≠ Usage Rights".

( 2 comments | on HN )

Re:Why RCF > other code protections by rcf-protocol on Thursday April 23, 2026 @12:31PM (#47877767)

RCF Firmware• Aurora A-VM — safe sandbox for signed .acode modules • Dilithium2 PQC signatures (protected today) • RCF Hardware Protocol v1.2.9 (SDIO/SPI/UART via secure opcodes) • RCF Bunker — zero-leakage crypto enclave Enforces RCF-PL v2.0.3 at hardware ``` https://aliyev.site/rcf ```

[ Parent | on HN ]

Re:Why RCF > other code protections by greton7 on Monday April 27, 2026 @05:06AM (#47919310)

what is RCF ? I have developed a tool promptCape https://gbreton7.gitlab.io/promptcape to protect against AI assistant (PI/RGPD/code) and it is so far used by companies which wants some level of protections as they do not control what is made of their data and code by AIs. Before that, some of them completely prohibited the use of non-local AI. They recently asked me to integrate promptCape as a terminal in cursor for claude code they have started to use. what do you think ?

[ Parent | on HN ]