Digital Fortress 🇺🇲
@DIGI_StakePool
Followers
2K
Following
12K
Media
111
Statuses
457
Stake Ada at https://t.co/GZGwQWAOMX. Family owned and operated bare metal Cardano stake pool by Rick, Christian, and Kyle McCracken. Blocks made in the USA.
United States
Joined June 2021
The Midnight testnet has massively improved the past year. The Midnight devs put in a lot work, and Digital Fortress Midnight nodes are running nice and smooth. I'm getting pumped for the mainnet launch 🚀 Make sure to claim your NIGHT tokens, this is going to be epic! Link 👇
Running Midnight
14
22
182
This is Cardano's use case @DOGE 🇺🇸 And, with the ultra high speed Hydra layer 2, speed is an advantage.
Now that @realDonaldTrump is becoming more involved in crypto, I just want to point out that there is no better blockchain for the US government to build on than Cardano. Its foundation was built with this capability in mind.
21
121
789
Now that @realDonaldTrump is becoming more involved in crypto, I just want to point out that there is no better blockchain for the US government to build on than Cardano. Its foundation was built with this capability in mind.
60
146
1K
All Digital Fortress Cardano nodes across the mainnet, preview, pre-production, and Sanchonet networks have been updated to Cardano-node version 10.1.4.
0
3
29
Digital Fortress Cardano stake pools are ready for the Plomin Hard Fork decision deadline for January 24, 2025. All nodes were updated to version 10.1.3, and "Yes" votes for delegated Ada stake weight was cast in December 2024.
0
3
21
Digital Fortress voted Yes to activate the Plomin Hard Fork. The Plomin Hard Fork enables full CIP-1694 governance functionality, including DRep voting on all actions, treasury withdrawals, constitutional updates, and votes of no confidence, while also introducing new Plutus
0
5
25
All Digital Fortress Cardano main net servers are upgraded to Cardano-node 10.1.3 Ready for the #PlominHardFork
2
1
28
All Digital Fortress nodes are migrated to Cardano node 10.1.2. Ready for Chang 2 #Cardano 😎
3
12
107
@elonmusk I highly recommend Charles Hoskinson (@IOHK_Charles) for the role of cryptocurrency policy advisor as this industry is approaching $3 Trillion dollars in value. He has been working in the industry for about 14 years, co-founder of Ethereum and founder of Cardano. Broad and deep
96
242
2K
You can easily stake directly from the website with many of Cardano's most popular mobile and browser wallets:
0
0
2
Check out our new website 👉 https://t.co/QAFWVsdjPh Works great on desktop and mobile wallet dapp browsers.
1
0
19
Digital Fortress voted "Yes" on the Chang 2 Hard Fork initiation on the Preview testnet. SPOs must be on version 10.1.1+ for the hard fork to execute. Govtool proposal data and action ID at this link: https://t.co/hd9Rc9lmOC
2
14
51
Cardano Summit Dubai 2024 is kicking off! 🚀
33
71
681
My preferred goals for DReps to advocate for are as follows: Cardano Dominance Ensure Cardano remains a dominant and competitive blockchain platform in a rapidly evolving space, adapting to the ever-changing needs of users and businesses. Good User Experience Simplify the
22
19
192
This is it #Cardano peeps. Today is the day! 🔥 The Chang hard fork activates Plutus v3 with these capabilities: Advanced Cryptographic Primitives: - Support for BLS12-381 curve pairings, enabling efficient zero-knowledge proofs and enhanced security. - Blake2b-224 hash function
33
203
860
Reminder: You do not have to delegate to a DRep. Cardano users will be able to vote on Governance Actions directly. I highly encourage as many people as possible to participate in Direct Voting. https://t.co/QLpavy58OU
19
78
300
We're thrilled to announce that Digital Fortress has never needed a "Tech Janitor" to run our pools! Our infrastructure is built in-house for our pools and other Cardano services, with love and lots of coffee ☕️. We promise we’re not just hitting "run" on someone else's scripts.
There is a very good reason for this... The SPOs aren't supposed to have a say in these parameters. In fact, after seeing this post from @_KtorZ_, I now believe it was a mistake to give SPOs a say in the Security Parameters. For a bit of history: The "Security Parameter"
1
3
31