fatih ince (@fince81) profile picture
Joined June 2009
fatih ince retweeted
Happy sunday all. We are targeting an assortment of updates this week that will focus on refining the Dot ecosystem from top to bottom. Additionally, we will be sharing more information on our Dot-Mistral 24B. We look to continuously push the boundaries on what we can achieve, ensuring we offer the very best prices, privacy, technology and tools available to our users. As our user base, usage, and token consumption grows, we will ensure we are bringing the highest quality of cutting edge technology to our users. Forward.
5
10
1
50
3,311
fatih ince retweeted
A fully agentic coding ecosystem where you can ask, build, iterate and create anything, in complete privacy. And you can do all of this, cheaper than anywhere else. We’re coming.
2
14
51
1,823
Axiom just made Robinhood trading effortless teapawt.org/AxiomExchange/status/2…
🌿HOOD, now on Axiom. $100k, first come first serve!
43
RT @stagedhappen: We've now accrued $26,000+ in total inference commitments across the Dot ecosystem, including a $15,000 enterprise agreem…
1
2
fatih ince retweeted
We've shipped another round of DotCode upgrades, including GLM 5.2 support and contextual workspace uploads. You can now use: - screenshots as visual references - product images for landing pages - CSVs for charts and reports - PDFs and docs for research/build tasks - source files for debugging - zipped projects for continuation or repair This ensures your uploads become part of the execution sandbox. Your agents can now inspect files, navigate project structure, edit code, run terminal commands, build, test, and continue from the same workspace. Flow: Prompt + Files
→ Private Sandbox
→ DotCode Agent
→ Filesystem + Terminal
→ Build / Test / Preview
→ Downloadable Project This brings DotCode closer to a true coding-agent workflow, where the agent works from real project context—not just prompts.
2
18
4
65
5,236
It’s official.. The Covenant Foundation is now using @nvidia’s ecosystem to help support its ventures via the NVIDIA Inception Program!
14
13
2
66
11,744
… @AlexJFRSalsali dropped a sneak peek of the first draft of our whitepaper…
This quoted post is unavailable.
3
4
24
1,841
fatih ince retweeted
So proud to be a @LaunchCovenant Founding Venture!
Gmgm. Been watching an impressive agentic project for the past 2 days 👇🏻 y4JiNFzBPofqiCpuDTcVq11nhUDQoDzeK1UBCoXxF9y Currently at 670k marketcap. LaunchCovenant (@LaunchCovenant) is an agentic governance layer and research lab developing a constitutional framework for AI agents and ventures. The framework overlays any base model to improve performance, alignment, and operational reliability. It draws on proven historical patterns of human organizational governance for practical deployment in multi-agent systems. Founder: Alex Salsali (@AlexJFRSalsali) is a University of Waterloo MBET graduate with a background in data analytics and product development. A serial builder with experience in blockchain and AI transparency projects (including Eunoia Labs), he leads the foundation, maintains the core framework, operates initial ventures, and supports selected external builders. Recent ventures on the Covenant network: useWedFlow (@useWedFlow): A coordination platform for the wedding industry that serves as the first live venture. It functions as a concierge service enabling text-based coordination among couples, guests, vendors, and inner circles. Currently in paid beta with limited spots. AquaFlow Intelligence: An AI decision-support system for water and wastewater operations, providing real-time guidance, process optimization, and automated audit logs. Led by industry veteran Hamid Salsali, it is revenue-positive with a Northern Ontario municipal client, has secured a $350K grant from the Ontario Centre of Innovation, and is expanding to additional municipalities and private-sector mining wastewater. It has drawn interest from clean-tech investors. Revenue streams for the network: Associated ventures contribute a revenue share back to the foundation. Operators can license the enhanced Tier II (production-ready) version of the framework, while the core remains open source. These flows support ongoing research, development, and treasury management. $CVT serves as the token that aligns incentives across the ecosystem. Personally at this level its still undervalued consider the founder's background and their ventures. This would definitely be a multi-million MC project.
4
4
28
2,415
Could this be about us? @AlexJFRSalsali
White paper incoming..
6
3
2
27
2,330
No words needed.
$CVT = @LaunchCovenant CoVenanT $CVT = Conviction ConVicTion coincidence? ♾️
3
3
19
1,451
fatih ince retweeted
🧵Covenant Foundation $CVT Thesis: TLDR: A solo founder just shipped a governance framework for AI agents that beats vanilla Claude Code by 9.4 points and ad-hoc baselines by 25 points on Terminal-Bench 2.0 , built in a single session.. He has a @ycombinator interview secured, @EasyA_Kickstart backing him, and a real product (@useWedFlow ) already live under the umbrella. $CVT is the coordination layer for what comes next
7
18
7
77
20,327
Hey guys will you be there? Let’s talk privacy payments with @radrdotfun [REDACTED] Set your reminder teapawt.org/i/spaces/1vOGwdyvYevJB
18
33
3
95
5,235
Introducing: The LiveSuite API Flywheel One of the incredible modules that LiveSuite offers is our API which provides data that no other platform has. Payments made for API access will automatically swap 50% into $LIVE, creating our first of many flywheels. We've also bought back 2.6M $LIVE through our treasury to celebrate this milestone.
5
6
22
1,151
QNet MAJOR FEATURES: Compact Hybrid Signatures - Reduced signature size from 12KB to 3KB (75% bandwidth savings) - Certificate caching with LRU eviction (5,000 capacity) - LZ4 compression: 70% memory reduction (5KB to 1.5KB) - Zero cache for Light nodes (mobile optimization) Progressive Finalization Protocol (PFP) - Self-healing consensus recovery - Degrading requirements: 80% → 60% → 40% → 1% node participation - Accelerating timeouts: 30s → 10s → 5s → 2s - Zero-downtime: microblocks continue during macroblock recovery Six-Layer Certificate Protection 1. Node identity verification (anti-spoofing) 2. Age verification: 2-hour max (anti-replay) 3. Expiration checks (1-hour certificate lifetime) 4. Clock skew protection (60-second tolerance) 5. Real CRYSTALS-Dilithium3 verification (async) 6. Producer match verification Optimistic Certificate Acceptance - Two-tier cache: pending + verified - Eliminates race conditions - Zero consensus delays - Byzantine-safe (2/3+ agreement) CRITICAL FIXES: Dilithium Signature Verification - Fixed double-hashing: SHA3(SHA3(block)) → SHA3(block) - Signatures validate correctly across all nodes Macroblock Signature Hashing - Fixed hex string handling: decodes to raw bytes before signing - Ensures consistent network-wide verification SECURITY: Reputation System - Invalid certificate: -20% reputation - 5 invalid in 10 minutes: 1-year ban - Certificate spoofing: instant permanent ban - Consensus threshold: 70% minimum reputation NIST/Cisco Compliance - CRYSTALS-Dilithium3 (NIST FIPS 203, 2420-byte signatures) - SHA3-256 unified hashing (NIST FIPS 202) - Encapsulated keys: Dilithium signs ephemeral Ed25519 - Dual signatures: classical AND post-quantum on every message - Forward secrecy: 1-hour certificate rotation SCALABILITY: O(1) Memory Scaling - 5 nodes: 5 certificates - 1,000 nodes: 1,000 certificates - 1,000,000 nodes: 1,000 certificates (validator sampling) - 100M nodes: 1,000 certificates - Constant 7.5 MB memory footprint Node Optimization - Light: 0 cache (no consensus) - Full/Super: 5,000 active + 2,000 disk-persisted ARCHITECTURE: Defense-in-Depth - P2P layer: full crypto verification (Dilithium3 + Ed25519) - Consensus layer: structural validation + Byzantine agreement - Only verified blocks participate in consensus 16 files changed, +2965/-538 lines github.com/AIQnetLab/QNet-Bl… github.com/AIQnetLab/QNet-Bl…
🤖 Made with AI
6
11
3
25
2,578
QNet Blockchain: Security & Architecture Update 1. Client Transaction System Implementation Mobile/Browser Transaction Handling: - Implemented Ed25519-only signatures for mobile and browser wallets - Added sendQNC method for QNC transfers with proper signature verification - Fixed claimRewards to create RewardDistribution blockchain transactions for full transparency - Updated transaction signing message format for client-server consistency - All transactions now require signature + public_key parameters Architecture Decision: Clients use pure Ed25519 (20μs operations) for optimal mobile performance, while blockchain nodes use Hybrid (Ed25519 + Dilithium) for quantum resistance. 2. NIST/Cisco ENCAPSULATED KEY Implementation Critical Security Fix: The hybrid certificate creation was using STRING format instead of RAW bytes for the Ed25519 public key, violating NIST/Cisco standards for encapsulated keys. What Was Fixed: ``` BEFORE: Dilithium signs "CERTIFICATE:node_id:hex_key:timestamp" AFTER: Dilithium signs [32 bytes Ed25519 key][node_id][8 bytes timestamp] ``` Now fully compliant with NIST/Cisco hybrid cryptography standards. Certificate format matches verification across all 3 verification points in the codebase. 3. Transaction Validation Hardening Security Improvements: - Removed validator stub that accepted invalid signatures during testnet phase - Implemented strict Ed25519 cryptographic verification using ed25519-dalek - All RPC endpoints now enforce signature and public_key requirements - Added verify_ed25519_client_signature for client-side message verification - Fixed validator to reject transactions with missing or invalid signatures Impact: Transaction validation now uses production-grade cryptographic verification instead of testnet stubs. 4. Hybrid Cryptography Architecture Validation Confirmed Implementation: - Every consensus message is signed by BOTH Ed25519 AND Dilithium - ENCAPSULATED KEYS implemented per NIST/Cisco recommendations - Forward secrecy with 1-hour certificate rotation - Certificate caching for O(1) verification scalability - Byzantine-safe consensus requiring 2/3+ honest nodes Quantum Attack Protection: To compromise QNet consensus, an attacker must break: 1. Dilithium signature on certificate (quantum-resistant) 2. Ed25519 signature on message 3. Dilithium signature on message (quantum-resistant) This dual-signature requirement makes quantum attacks infeasible. 5. Certificate Distribution System Why Certificates Were Implemented: QNet uses ephemeral Ed25519 keys for performance (20μs vs 2ms for Dilithium), rotated every hour for forward secrecy. Each ephemeral key must be signed by the node's permanent Dilithium key to prove authenticity. This creates a certificate that other nodes cache for fast verification. Current Implementation: - Certificates broadcast in 3 scenarios: immediate (when becoming producer), periodic (30s), and rotation (3600 blocks) - Added immediate certificate broadcast when node becomes producer to prevent verification delays - P2P certificate distribution with rate limiting and caching Currently conducting debugging and optimization of certificate synchronization under various network conditions. 6. F-Droid Build System Still working through F-Droid's specific build requirements and lifecycle. Their build system has unique constraints around npm dependency installation and React Native integration that require careful configuration of prebuild steps and directory structure. github.com/AIQnetLab/QNet-Bl…
11
15
1
40
2,884
QNET: Post-Quantum Decentralized Network Phase 1: 1DEV Token Built on Solana as SPL token. Users burn 1DEV to activate nodes in upcoming QNET blockchain. Current cost: 1,500 1DEV (~13cents) for unlimited mining access. Price decreases as more supply burns - creating deflationary economics. Phase 2: QNC Native Token Triggers when 90% of 1DEV burned OR after 5 years from genesis. QNC (QNET COIN) becomes native currency with 4,294,967,296 max supply (2^32). Features unique "Sharp Drop" halving - rewards halve every 4 years, then drop 10x at year 20, then resume halving. Three Reward Pools: Pool #1: Base emission (starts 251,432 QNC per 4h, halves every 4 years) Pool #2: Transaction fees (70% to server super nodes, 30% to full nodes) Pool #3: Node activation fees redistributed to ALL active participants (Phase 2 only) No Staking Required Uses reputation system instead of locking tokens. Mobile light-nodes get equal rewards as servers. Participation based on reliable behavior, not capital. Key Innovation: Phase 1: 1DEV tokens are burned for node activation. Phase 2: node activation requires QNC payment to Pool #3. Both phases designed for fair distribution without traditional venture capital funding or premine. This experimental approach proves independent developers can create advanced blockchain technology using modern AI tools. #QNET #BLOCKCHAIN #QUANTUM #WEB3 #AI
41
28
5
110
42,015
$ISENS flywheel sneak peak🔥
3
3
22
959