QuByte

The first coin launched from a Falcon-512 identity.

[QuByte @QuByteApp]

$BYTE is live

CA: QUALaRd6ZvZkt9NqJjVVN3MP23RtFNwDbJc3VDHcHwN

launched from a falcon-512 key. a quantum computer can't fake this launch, and nobody can pull the fees out. they only get burned.

[QuByte @QuByteApp]

@soleater74 buy and burn -

[QuByte @QuByteApp]

Anyone can run a claim. 80% of the vault buys the coin and burns every token bought; 20% goes to the treasury 🤝

[QuByte @QuByteApp]

@Yourbeingrugged

[QuByte @QuByteApp]

Anyone can run a claim. 80% of the vault buys the coin and burns every token bought; 20% goes to the treasury 🤝

[QuByte @QuByteApp]

104.79M $BYTE Burned 🔥

[QuByte @QuByteApp]

I can’t blame them, but what you’re doing is really hurting people who are trying to build something. Teams can’t influence the price unless they create an 80% bundle. In fact, it’s not the projects that go for millions from day one that are valuable—it’s the ones that are developed steadily. The ones that go for millions from day one will be worthless within a few days.

As for @toly , Solana has truly built an amazing ecosystem where developers (especially the major ones) are always ready to support newcomers. Toly is one of them.

[crippling gambling addiction @yung_stony]

@QuByteApp I mean can you really blame them 99% of these things end up being just that “a rug”this thing dumped hard regardless of 10% being burnt. And tbh obviously this is a matter of opinion but it seems like this things success hinders on a @toly reply

Which like never happens

[QuByte @QuByteApp]

There’s a large group of people on Solana who believe that every project’s development will end in a “rug pull.” We see a group that’s hoping for this more than just supporting it. Qubyte is the first team to implement quantum resistance with Falcon. We see this not just as a launchpad, but as the future of wallets with quantum encryption. This was actually the first phase of testing Falcon, and it was truly very successful. Stay tuned for further announcements.

[Cryptimus Maximus @StefanoC0612]

@QuByteApp Finally rugged lol

[QuByte @QuByteApp]

gByte

[QuByte @QuByteApp]

Why not ?

[toly 🇺🇸 @toly]

@PospisilAdam @mert @MrShrubs @deanmlittle Why not falcon?

[QuByte @QuByteApp]

Falcon will make it.

[toly 🇺🇸 @toly]

@L0STE_ @deanmlittle Do you think falcon will make it?

[QuByte @QuByteApp]

We understand your concerns, but as a team, we’re continuing to work on development behind the scenes. We don’t believe constantly posting just for the sake of posting is productive, as it can easily turn into spam. Instead, we’ll keep you informed of our progress and share updates with you periodically. Thank you for your patience and continued support!

[Feli @feliisreal1]

@QuByteApp post more

[QuByte @QuByteApp]

9.0% of the original supply, gone for good. 909.98M BYTE remain in circulation.

[QuByte @QuByteApp]

Can we all agree on falcon?

[toly 🇺🇸 @toly]

@kostascrypto @matteodotsui Can we all agree on falcon? It’s our chance to just have one set of bugs to worry about.

[Yuki at CAC and DevRel at Solana Foundation @yuki_web3_jp]

To everyone who loves Solana — a few words on why Transaction v1 matters for post-quantum cryptography🔥

Look at the constraints table in SIMD-0385. Maximum transaction size: 4,096 bytes, up from 1,232.

Now consider Falcon-512. It's one of the schemes NIST selected for post-quantum signature standardization, though the standard itself — FIPS 206 — is still in draft and hasn't been finalized.

Falcon-512 uses an 897-byte public key and a 666-byte signature: 1,563 bytes together.

That single signature exceeds the old 1,232-byte ceiling on its own — before any instruction data, before the fee payer's own signature. For comparison, Ed25519 needs 96 bytes in total.

So it simply couldn't fit, no matter how much anyone wanted it to. Transaction v1 is what changes that.

Two things worth being precise about. Even in v1, the signature field itself is still an array of 64-byte Ed25519 signatures — Falcon would ride along as instruction data.

And which post-quantum scheme gets adopted is still undecided.

Still, going from "it physically cannot fit" to "it fits" is real progress.

This is the kind of foundational work that keeps happening on Solana.

I'm based in Japan, and I'll keep working with Superteam Japan to bring this kind of knowledge to a Japanese audience — accurately.

========================
Solanaを愛する皆さん、Transaction v1が耐量子暗号にとってなぜ重要なのか、少し語らせてください🔥

SIMD-0385の制約表を見てください。トランザクションの最大サイズが、1,232バイトから4,096バイトになります。

そしてFalcon-512。NISTが耐量子署名として標準化する方式に選んだもののひとつです（規格自体はFIPS 206として現在ドラフト段階で、最終版はまだ出ていません）。

このFalcon-512は、公開鍵897バイトに署名666バイトで、合わせて1,563バイト。署名ひとつだけで、旧上限の1,232バイトを超えてしまいます。

命令データを載せる前、手数料支払い用の署名を入れる前の段階で、です。ちなみに現行のEd25519は、公開鍵と署名を合わせて96バイトです。

つまり、載せたくても物理的に載らなかった。そこを変えるのがTransaction v1です。

正確を期すために2点。v1でも署名欄そのものは64バイトのEd25519署名の配列のままで、Falconは命令データとして載る形になります。

そして、どの耐量子署名方式を採用するかはまだ決まっていません。

それでも、「物理的に入らない」から「入る」へ進んだことは、確かな前進だと思います。

Solanaではこうした基盤の部分での進化が起こり続けています。

私は日本を拠点に活動しているので　@SuperteamJapan と協力しながら、#Solana の知見を正しく日本語で伝えていきます！

[QuByte @QuByteApp]

$BYTE program upgrade authority is now a squads vault with a 7 day time lock. any change waits a week on chain before it can run.

handover: https://t.co/7rR8AvwNWa

time lock: https://t.co/PzPzTsLjB6

[QuByte @QuByteApp]

@1krispy1 Working

[QuByte @QuByteApp]

launches are open.

sign your coin with a falcon-512 key, we check it on chain, https://t.co/E2LJzF0mw8 creates it. 80% of creator fees buy it back and burn it.

https://t.co/uWtZo9hpeE

[QuByte @QuByteApp]

@Doeyor It is currently being fixed

[QuByte @QuByteApp]

@pallets cf R2 and indexer configurations are all that's remaining, and they will be active within a maximum of 1 hr

[QuByte @QuByteApp]

Anyone who wants the “Claim” button to be active without permission can trigger it. +-+