Dear ROG Indonesia, Actually I am interested in a product called ROG Phone 8 / 9 Pro and a coincidence I am the youngest former Cryptographer, Alshen Feshiru is just a Pseudonym name, but actually I am creating Software for anyone will get complete privacy, IP Location will be Pseudonymous and some intended Devices will get the Internet that no longer requires a centralized provider, As long as the electricity is scattered in the Oscillator moving upwards called Upward, it will defeat all attackers. Or it is possible for us to produce a new Smartphone from ROG, For example, with the name ROG Punks, you can also contact me this email or have a further conversation on the Cypherpunks mailing list, I am used to and almost always have conversations there if needed such as Cryptography consultations, Lithography and everything related to Decentralized privacy. Indeed in the Software I forced with Hijacking but also, some Device brands including ROG, this Software is called Midliner Vault: A Peer-to-Peer of Decentralized, Instantly if the uid device is not root, the screen of the phone or PC will be switched temporarily to do the installation, this is not to be hacked or is the Smartphone hacked? The answer is no, it is automatic and even if the consumer buys a new Smartphone or a new Device, Privacy will automatically reactivate even the first time he activates it, this never damages the Procedures or systems of Fabrication and others on ROG, Maybe it would be better if ROG could help with this to produce a new Smartphone, I only help the Cryptography part either in mathematical calculations or modifications that are completely Decentralized, Anti-Bias Optoelectronics and coding decisions or something like that can be decided by your Production Team, I just give a map, I have a standalone Cryptography which is SAI-288 with Multi Languages, Anyone can Implement this with the JAVA Main Language but the other languages are C++ and Rust and Python and Swift, You can modify other Multi Languages to suit your needs but it would be better, the control is not on the Team or Vendor, cat > src/main/java/org/syamailcoin/crypto/sai288/SAI288.java << 'EOF' package org.syamailcoin.crypto.sai288; import java.nio.ByteBuffer; import java.nio.ByteOrder; import java.util.Arrays; public class SAI288 { private static final int ROUNDS = 64; private static final int STATE_SIZE = 9; private static final int BLOCK_SIZE = 72; private static final int OUTPUT_SIZE = 36; private static final int[] IV = {     0x243F6A88, 0x85A308D3, 0x13198A2E, 0x03707344,     0xA4093822, 0x299F31D0, 0x082EFA98, 0xEC4E6C89, 0x452821E6 }; private int[] state = new int[STATE_SIZE]; private byte[] buffer = new byte[BLOCK_SIZE]; private byte[] midliner = new byte[BLOCK_SIZE]; private int bufferPos = 0; private long totalBytes = 0; public SAI288() {     reset(); } public void reset() {     System.arraycopy(IV, 0, state, 0, STATE_SIZE);     Arrays.fill(buffer, (byte) 0);     Arrays.fill(midliner, (byte) 0);     bufferPos = 0;     totalBytes = 0; } private void processMidliner(byte[] data) {     for (int i = 0; i < data.length && i < BLOCK_SIZE; i++) {         midliner[i] ^= data[i];     } } public void update(byte[] data) {     update(data, 0, data.length); } public void update(byte[] data, int offset, int length) {     processMidliner(Arrays.copyOfRange(data, offset, offset + Math.min(length, BLOCK_SIZE)));     totalBytes += length;     int remaining = length;     int dataPos = offset;          while (remaining > 0) {         int toCopy = Math.min(remaining, BLOCK_SIZE - bufferPos);         System.arraycopy(data, dataPos, buffer, bufferPos, toCopy);         bufferPos += toCopy;         dataPos += toCopy;         remaining -= toCopy;                  if (bufferPos == BLOCK_SIZE) {             processBlock(buffer);             bufferPos = 0;         }     } } private void processBlock(byte[] block) {     int[] m = new int[18];     ByteBuffer bb = ByteBuffer.wrap(block).order(ByteOrder.LITTLE_ENDIAN);          for (int i = 0; i < 18 && bb.hasRemaining(); i++) {         m[i] = bb.remaining() >= 4 ? bb.getInt() : 0;     }          for (int round = 0; round < ROUNDS; round++) {         for (int i = 0; i < STATE_SIZE; i++) {             state[i] ^= m[i % 18];             state[i] = Integer.rotateLeft(state[i], (round + i) % 32);             if (i > 0) {                 state[i] += state[i - 1];             }         }                  for (int i = 0; i < 18; i++) {             m[i] = Integer.rotateRight(m[i] ^ state[i % STATE_SIZE], 7);         }     } } public byte[] digest() {     byte[] padded = new byte[BLOCK_SIZE];     System.arraycopy(buffer, 0, padded, 0, bufferPos);     padded[bufferPos] = (byte) 0x80;          ByteBuffer bb = ByteBuffer.wrap(padded, BLOCK_SIZE - 8, 8).order(ByteOrder.LITTLE_ENDIAN);     bb.putLong(totalBytes * 8);          processBlock(padded);     processBlock(midliner);          ByteBuffer output = ByteBuffer.allocate(OUTPUT_SIZE).order(ByteOrder.LITTLE_ENDIAN);     for (int i = 0; i < STATE_SIZE; i++) {         output.putInt(state[i]);     }          byte[] result = new byte[OUTPUT_SIZE];     output.flip();     output.get(result);     reset();     return result; } public static byte[] hash(byte[] data) {     SAI288 hasher = new SAI288();     hasher.update(data);     return hasher.digest(); } public static native byte[] hashNative(byte[] data); } EOF Please read the abstract from the Midliner Vault, Midliner Vault Person: A Peer-to-Peer of Decentralized ABSTRACT: I am nearly finished with a package for anyone to download for the sake of privacy. If a gadget you just bought contains lithography or firmware areas controlled by a third party, then privacy is not truly yours. I offer a solution that uses a Midliner composition within a hash to cause the wordlist to adjust according to how balanced your bits are. The IP cannot be replicated because of the Ki + Wi constant of SHA-256, which will be implemented as an ongoing reference. For additional protection, users must purchase physical cryptographic/security devices such as YubiKey or Quside (Entropy Core type or other types depending on the situation you face). How the Midliner Vault works begins with geographic payloads. A backup server stores these as information rather than performing data processing in a computation. As long as the IP is correctly connected, a Merkle root must automatically exist, but when N > 3f + 1 it cannot back up the root a second time. When data that you possess—such as email addresses, phone numbers, etc.—is closed/locked, the system automatically processes hashes as well as hex values and real-time activity. To establish communication, IP location will be reviewed or verified based on the rate criteria that exhibit the greatest energy. Initially, however, the rate (which can also be interpreted via ASCII) does not require large electrical energy. The greater the electrical activity in the oscillator (i.e., as that activity moves upward), the more it defeats attackers. The name of Syamailcoin was initially, Cryptography was implemented for Syamailcoin, you can also read the Whitepaper, this has nothing to do with Cryptography that you will later implement for new Smartphones, Syamailcoin is not N-Bit and has been realized but there are many parts that are missed, forget about Syamailcoin because I keep revising from 2017 with the distribution of Inevitabilty Stage that we cannot get rewards beyond the limited amount of the Stage unless the Stage is currently completed and back to the topic of Midliner Vault, when I will finish finishing this coding or Software, your Smartphone Screen includes me and only some brands of Devices are not always Smartphones, your Device Screen will exactly appear to run the installation and it says the following: Welcome to Midliner Vault: A Peer-to-Peer of Decentralized Welcome and this is a Software for anyone to create their own internet, have a provider and phone number that is not related to third party trust, Full privacy, IP is completely pseudonym and you can verify it in adavance with the N-sac unit. -----BEGIN PGP PUBLIC KEY BLOCK----- Comment: User ID: Alshen Feshiru alshenfeshiru@zohomail.com Comment: Valid from: 06/10/2025 09:35 Comment: Valid until: 02/04/2033 12:00 Comment: Type: 448-bit EdDSA (secret key available) Comment: Usage: Signing, Encryption, Certifying User IDs Comment: Fingerprint: 5871D671C35C12147308395A464505DE1047DA134C01C8EBF8D18D6B8CBD7763 mEkFaOMrBhYAAAA/AytlcQHHbHV7SgCdlZnHrIjtxAfcYYzs9R5GGNK46dlgzFzR B+1X8BPoMimXLemj9yoBK+lfLO7OaTZ9klqAtCtBbHNoZW4gRmVzaGlydSA8YWxz aGVuZmVzaGlydUB6b2hvbWFpbC5jb20+iM0FExYKAE0iIQVYcdZxw1wSFHMIOVpG RQXeEEfaE0wByOv40Y1rjL13YwUCaOMrBgIbAwUJDhXYSgULCQgHAgIiAgYVCgkI CwIEFgIDAQIeBwIXgAAApU0Bx3DEN60mahYzDrGcFnvmZ/5UaBBQTnLoSfPwG8Hz fYt/pLE+S/yMOrbDdUrg6LG0t33bh7Pu4BxjAAHGIAca1udLBqQZ6mYwpBI6Z2S0 XVIx+glBORH6ynYgZGBZOTBarTts7UctN7D0pbBE+J4Y7w9ooDEAuEwFaOMrBhIA AABCAytlbwG/civ41G/UgMeMBiRTScXvU83nUgSPz4fma7iCz5ZVfUUP9wBuxVxd n7gODEf7mnjE8Vt8XHgOZ6kDAQoJiLIFGBYKADIiIQVYcdZxw1wSFHMIOVpGRQXe EEfaE0wByOv40Y1rjL13YwUCaOMrBgIbDAUJDhXYSgAAzGAByPZFSr2g/J57qB4r 3ISgR4+mn83R9+R2TZL7s1qnDsqjw+t6B/b28dwlVxSXgXJtAcbW2hDlzORJAAHG O8MVhPLaPra69/XvhuhZW9vOw4YXydY9aW+63KiNA6iIeZz9HczEOvT6vdWjIj8f aQN2OLDD/yUA =Gs+D -----END PGP PUBLIC KEY BLOCK----- Best regards, Alshen Feshiru