tGt

2.5K posts

tGt banner
tGt

tGt

@TGamblernetwork

tGt a natural token on Joyful On-chain Applications JoyFI

Galaxy Katılım Kasım 2023
5 Takip Edilen4.3K Takipçiler
Sabitlenmiş Tweet
tGt
tGt@TGamblernetwork·
#tGt | Listing Is Live tGt is now LIVE on Uniswap V2 (Ethereum Mainnet). Trading has officially started. 🔗 Pair address: 0x4dfaB88f9415D3Ad67f83796dd79DdD7cf2c7573 This is a fair launch: No privileged groups No early access No backroom deals ⚠️ Please note: Initial liquidity is low High volatility is expected Trading bots may cause short-term price movements Ownerless smart contracts. Fixed & immutable supply. Everything is on-chain and verifiable. Watch the chain before the chart. 🃏
English
26
13
58
6.2K
tGt
tGt@TGamblernetwork·
We have 1,160,000 tGt ready to be distributed. Drop your ETH address below 👇 🔁 Share this post 👤 Follow us 🎁 A surprise is waiting for you. #tGt #JoyFi #Community
English
220
203
250
7.3K
tGt
tGt@TGamblernetwork·
We will build trust over time, and "value" through utility and code. We are here and will continue to build blockchain technologies to create value. #CommunityJoy #tGt
English
1
0
10
288
tGt
tGt@TGamblernetwork·
Transparency Statement: Smart contracts allocate 49 million tGt to the team, 80 million tGt to development, 335 million tGt to liquidity support contracts, and 300 million #tGt to the Random Reward program. Currently, 236 million tGt are in circulation on the open market.
tGt tweet media
English
4
4
12
505
tGt
tGt@TGamblernetwork·
If we liked your previous comment on our posts, it means you might be one of today’s lucky followers. Our team distributed the tGt tokens allocated for the airdrop randomly. Remember, we give positive priority to users who follow us closely, stay active, and support our posts. The airdrop may arrive a bit later, but it will not be forgotten. Keep following us #tGt 🚀💛 etherscan.io/tx/0x6b0435471…
English
5
3
15
399
tGt
tGt@TGamblernetwork·
We've created nominal value for tGt, even if it's on a microcap scale. Now it's time to create a benefit, some fun, and a difference. thegamblertoken.eth.limo
English
0
3
7
211
tGt
tGt@TGamblernetwork·
Our recent airdrops will be distributed soon. ☀️ Stay connect 💫
English
4
2
14
505
tGt
tGt@TGamblernetwork·
Gm everyone ☀️
English
3
0
8
162
tGt
tGt@TGamblernetwork·
A fair internet, an uncensored internet, a secure internet. Web3 is the only way.
English
1
1
8
173
tGt
tGt@TGamblernetwork·
Gm Everyone ☀️
English
3
0
12
158
tGt
tGt@TGamblernetwork·
As the tGt team, we pray for all civilians amidst the ongoing violence, and we call for a world where mutual love and tolerance prevail instead of radicalism, and science and art instead of war and conflict. 🕊️
English
0
0
10
217
tGt
tGt@TGamblernetwork·
Hello everyone ☀️ ⚡Drop your eth adress ⚡Share this post. We have suprise for you. ☀️
English
141
92
118
3.9K
tGt
tGt@TGamblernetwork·
Random Reward Program – Announcement Our team continues to work on a long-term, fun-driven emission model for the tGt token, built around a gamified Proof-of-Stake consensus. Our goal is to move beyond the classical PoS structure and transform staking into an engaging, JoyFi-inspired experience 🫴🏻 without compromising robustness, predictability, or decentralization. Before publishing the full technical documentation, we are open to all feedback, suggestions, and critical perspectives from the community. We are building slowly. We are building transparently. We are building for the long term. #tGt #JoyFi #Web3 #ProofOfStake
tGt@TGamblernetwork

We’ve shared an update on the Random Reward Program design on GitHub. We’re moving away from fixed or guaranteed staking models and exploring an on-chain, ownerless random reward consensus for #tGt. Feedback and technical input are welcome. Join the discussion on #GitHub Random Reward Program – Consensus Update & Feedback · TGamblersteam/tGtRandomRewardProgram · Discussion #1 share.google/j3byOQVdfSWcjo…

English
1
2
6
356
tGt
tGt@TGamblernetwork·
@VitalikButerin Ethereum will overtake Bitcoin.
English
0
0
2
100
vitalik.eth
vitalik.eth@VitalikButerin·
Now, the quantum resistance roadmap. Today, four things in Ethereum are quantum-vulnerable: * consensus-layer BLS signatures * data availability (KZG commitments+proofs) * EOA signatures (ECDSA) * Application-layer ZK proofs (KZG or groth16) We can tackle these step by step: ## Consensus-layer signatures Lean consensus includes fully replacing BLS signatures with hash-based signatures (some variant of Winternitz), and using STARKs to do aggregation. Before lean finality, we stand a good chance of getting the Lean available chain. This also involves hash-based signatures, but there are much fewer signatures (eg. 256-1024 per slot), so we do not need STARKs for aggregation. One important thing upstream of this is choosing the hash function. This may be "Ethereum's last hash function", so it's important to choose wisely. Conventional hashes are too slow, and the most aggressive forms of Poseidon have taken hits on their security analysis recently. Likely options are: * Poseidon2 plus extra rounds, potentially non-arithmetic layers (eg. Monolith) mixed in * Poseidon1 (the older version of Poseidon, not vulnerable to any of the recent attacks on Poseidon2, but 2x slower) * BLAKE3 or similar (take the most efficient conventional hash we know) ## Data availability Today, we rely pretty heavily on KZG for erasure coding. We could move to STARKs, but this has two problems: 1. If we want to do 2D DAS, then our current setup for this relies on the "linearity" property of KZG commitments; with STARKs we don't have that. However, our current thinking is that it should be sufficient given our scale targets to just max out 1D DAS (ie. PeerDAS). Ethereum is taking a more conservative posture, it's not trying to be a high-scale data layer for the world. 2. We need proofs that erasure coded blobs are correctly constructed. KZG does this "for free". STARKs can substitute, but a STARK is ... bigger than a blob. So you need recursive starks (though there's also alternative techniques, that have their own tradeoffs). This is okay, but the logistics of this get harder if you want to support distributed blob selection. Summary: it's manageable, but there's a lot of engineering work to do. ## EOA signatures Here, the answer is clear: we add native AA (see eips.ethereum.org/EIPS/eip-8141 ), so that we get first-class accounts that can use any signature algorithm. However, to make this work, we also need quantum-resistant signature algorithms to actually be viable. ECDSA signature verification costs 3000 gas. Quantum-resistant signatures are ... much much larger and heavier to verify. We know of quantum-resistant hash-based signatures that are in the ~200k gas range to verify. We also know of lattice-based quantum-resistant signatures. Today, these are extremely inefficient to verify. However, there is work on vectorized math precompiles, that let you perform operations (+, *, %, dot product, also NTT / butterfly permutations) that are at the core of lattice math, and also STARKs. This could greatly reduce the gas cost of lattice-based signatures to a similar range, and potentially go even lower. The long-term fix is protocol-layer recursive signature and proof aggregation, which could reduce these gas overheads to near-zero. ## Proofs Today, a ZK-SNARK costs ~300-500k gas. A quantum-resistant STARK is more like 10m gas. The latter is unacceptable for privacy protocols, L2s, and other users of proofs. The solution again is protocol-layer recursive signature and proof aggregation. So let's talk about what this is. In EIP-8141, transactions have the ability to include a "validation frame", during which signature verifications and similar operations are supposed to happen. Validation frames cannot access the outside world, they can only look at their calldata and return a value, and nothing else can look at their calldata. This is designed so that it's possible to replace any validation frame (and its calldata) with a STARK that verifies it (potentially a single STARK for all the validation frames in a block). This way, a block could "contain" a thousand validation frames, each of which contains either a 3 kB signature or even a 256 kB proof, but that 3-256 MB (and the computation needed to verify it) would never come onchain. Instead, it would all get replaced by a proof verifying that the computation is correct. Potentially, this proving does not even need to be done by the block builder. Instead, I envision that it happens at mempool layer: every 500ms, each node could pass along the new valid transactions that it has seen, along with a proof verifying that they are all valid (including having validation frames that match their stated effects). The overhead is static: only one proof per 500ms. Here's a post where I talk about this: ethresear.ch/t/recursive-st… firefly.social/post/farcaster…
English
803
1K
5.7K
901.3K
tGt
tGt@TGamblernetwork·
Gm tGt community ☀️
English
2
0
4
113
tGt
tGt@TGamblernetwork·
Hello Blockchain community ☀️ We are going through dark times where morale is low and hope feels distant. The market is volatile, trust has been shaken, and many are exhausted. However, our focus is not on short-term exchange prices or daily market fluctuations. We are committed to building long-term structural solutions and creating sustainable value. For us, what truly matters is not the charts 🫴🏻but the foundation we build. Not temporary hype 🫴🏻 but resilient systems. In times like these, we double down on transparency, durability, and meaningful innovation. Because real value is built during crises. We are here. And we continue to build.
English
2
2
10
205
tGt
tGt@TGamblernetwork·
Gm tGt #Community ☀️ ⚡Airdrop events are coming to an end. ⚡A technical review of the Random Reward program is on its way. ⚡The markets breathed a sigh of relief; our comeback will be fantastic. Drop your eth adress, join #JoyFI universe 🔥
English
19
4
14
456