Aglovale

2.6K posts

Aglovale banner
Aglovale

Aglovale

@aglovale0x

Crypto tech enthusiast, Linux junky, $kas holder & contributor. quietly building...

USA Katılım Temmuz 2009
409 Takip Edilen795 Takipçiler
Sabitlenmiş Tweet
Aglovale
Aglovale@aglovale0x·
Public solo mining aggregated into one list: rkstratum.rustykaspa.org/bridges • Find a server close & start solo mining! • 0% fees via RKStratum - Keep all of your mining rewards! • Run a public kaspa node or stratum? Register it! • added an EU stratum: 'krypticc' ~Hosted 1Gbit/s~ credit to @dablacksplash for building an incredible tool!
English
0
3
13
670
Aglovale retweetledi
Ledger
Ledger@Ledger·
Fast, secure, and simple: swap Kaspa (KAS) in Ledger Wallet! No need to move your assets to an exchange. Approve your swap directly on your Ledger signer and keep your private keys offline 🔐 Head over to Ledger Wallet now to swap KAS.
English
85
149
466
21K
Aglovale
Aglovale@aglovale0x·
These are all publicly run solo mining stratum's. Same as the one embedded in the rusty-kaspa node. You connect your miner & use your wallet and theres no middle man, no fees. They are just publicly listed by volunteers & tracked by the website. The idea is to steer the masses away from pools & fees. I can't attest for stability/uptime of them all since they are run by volunteers, but you can use one and set 2 others as backup. 'krypticc' is hosted and mine.
English
1
0
1
70
₿RT 𐤊 🐈📈
New $KAS miner just joined the network who dis ⛏️
₿RT 𐤊 🐈📈 tweet media
English
11
13
142
3.8K
Aglovale
Aglovale@aglovale0x·
Looking like a strong month for Kaspa. Will $KAS hold .04 ? Are we finally breaking out? 648 days since Kaspa's last ATH.
Aglovale tweet media
English
2
4
76
1.9K
Aglovale
Aglovale@aglovale0x·
Re-working the payment model slightly before public testing. Trying to keep it simple: • x $KAS = 30 days access + 100 credits • 1 credit = 1 eth_sendRawTransaction • All other RPC calls are free • eth_getLogs limited to 10k blocks • Optional credit re-ups for power users Key lifecycle: • 3-day grace period after expiration • +30 day extension window • Then permanent key expiration + credit loss Longer activations: • 3x = 90d + 300 credits • 9x = 270d + 900 credits • 12x = 360d + 1200 credits Dashboard + endpoint will provide: • remaining credits • key expiration date • native $KAS deposit address Targeting end of week for limited public testing.
English
0
0
0
86
Aglovale
Aglovale@aglovale0x·
Running an @Igra_Labs node stack highlighted an interesting point for me: RPC providers must fund wallets & incur L1 kaspa:native fees to sequence L2 TXs. This led me down a rabbit hole where I started exploring a metered RPC model: • pay-per-call • accountless • native kaspa:native credits After a few days of building, I have a fully automated, accountless, credit based rpc proxy that utilizes native $kas for activation & credit reloads. If you would be interested in testing or providing feedback, I'm looking for a few active Igra L2 testers. It's currently not running in a production environment but I'm interested in outside perspectives. Interested & experienced web3/dapp/evm builders, shoot me a DM.
Aglovale tweet media
English
2
3
11
3.2K
Aglovale
Aglovale@aglovale0x·
Exciting features coming to kaspa:native with the upcoming Toccata hard-fork. As we learned with Crescendo's 1BPS to 10BPS; it will be a seemless integration after nodes are upgraded across the network.
Michael Sutton@michaelsuttonil

why I’m personally excited about Kaspa’s upcoming Toccata covenants - for the first time, I can build creative, complex apps directly over infrastructure I helped design and build - we designed under architectural constraints, but the result came out surprisingly expressive and powerful - Silverscript is cool as hell - I can literally open a *.sil file and write a complex contract that will be fully verified on Kaspa L1 - (nottoself: create a 10-minute video showing the building of such an app e2e) - I can design my own vaults and safeguards, and manage funds securely without risking a heart attack each time I touch a wallet - covenant ids, contract templates, and inter-covenant communication (ICC) feel like a new set of axioms, or a new algebra to work with and discover - sig verify from stack / sighash anyone-can-pay + covenant ids can allow interesting shared-state covenants (requires a non-consensus miner policy; kudos to @maxibitcat for pushing this line of thinking) - complex contract systems can be deployed in one spk hash. no storage rent, no deployment tax; users pay only the transient mass for tx data as they use it - as I’ve mentioned in the past, this becomes especially interesting for AI/agentic environments, where bots could cheaply create one-time agreements between themselves - I didn’t even mention based apps yet. That’s a whole vertical that isn’t ready for exploration yet, but will be very soon

English
0
0
2
87
Aglovale retweetledi
Luke Dunshea
Luke Dunshea@elldeeone·
Kaspa.org has been refreshed. Kaspa has a lot going on, but the main site does not need to put it all at the front door. Its first job is simple: help someone arrive, understand what Kaspa is, and know where to go next. The previous site accumulated more over time. Pages, explanations, resources, and audiences were added. This version starts smaller, so it can grow with Kaspa from here. The refresh is not just visual. The wording, structure, and narrative direction all needed attention IMO. The content traces back to @hashdag’s writing, simplified for a first read. Kaspa is already deep enough. The first read should not make people work harder than necessary. There are many true ways to talk about Kaspa, but Kaspa.org cannot carry twenty narratives at once. For this version, the strongest one to unify around is real-time decentralisation. Part of the refresh was also about making the builder path easier to follow. Kaspa.org gives people the overview of what exists, why it matters, and where to go next. Docs.kaspa.org gives builders the deeper material, with room for examples, detail, and ongoing improvement. Docs.kaspa.org starts with @IzioDev's work and has the broader goal of bringing important Kaspa L1 builder documentation into one place. Both repos are public. Pages will be added, wording will change, gaps will be filled, and the work can happen in the open. Big shoutout to @kasmediadotcom for their support in helping bring this refresh together. Have a look around. If you see something that can be better, please open an issue or PR.
English
92
262
728
53K
Aglovale retweetledi
Pavel Emdin
Pavel Emdin@emdin·
Thanks @KaspaSilver! Yes, multi-chain stablecoin to KAS and back in two clicks is one of our core use cases. Next thing to remove is the wallet UI. Here is the demo of an AI agent buying and selling KAS through Igra with no CEX in the loop and zero clicking around. Github with the skill, should work for any coding agent: github.com/emdin/igra-ski… Would love your opinion and community feedback.
Victor Resto@KaspaSilver

After testing both @kasplex and @Igra_Labs to acquire some more $KAS I have to say @Igra_Labs has a much smoother experience. Main reason being is that Kasplex only has stablecoin access via BNB which means I have to mess with pancake swap to get BNB USDC first. I am a @RobinhoodApp user primarily and I am more used to using USDC on polygon to move funds across applications. Igra allows me to skip one step and quickly go from stablecoin on polygon to stablecoin on igra. I am simply sharing my personal opinion with these L2s so that I have personal experience with them. I do not advocate for acquiring Igras token and I praise Kasplex for never having a token to begin with. This is also only surface level opinions based on user experience. The security and decentralization of these systems is something I definitely want to tackle in the future and give my opinion about which one is better but at the moment I lack understanding. At the very least these are L2 options and that comes with risks such as operations not entirely being trustless.

English
12
76
314
11.4K
Aglovale retweetledi
5bb55b
5bb55b@5bb55b·
github.com/5bb55b/go-kasp… go-kaspabook is a lightweight indexed kaspa REST-API system suitable for integration with dApps/CEXs/organizations (but not suitable as a data source for browsers). It is an early version, just about 10 days of work. I need a few more days to test it, then I will use it in several projects and observe how it performs. The API doc is currently generated by AI, I will optimize it later. Key features: Data fetching via Kaspad vspc2 (only focuses on the chain-blocks and the accepted-txns data.); Using the local RocksDB with support for daascore-to-live pruning; Using protobuf data format to save disk space; An aggressive data item storage strategy (more index-params will be added later to support additional data); Reorg processing mechanism for index-keys. book-API: GET - /book/status GET - /book/vspcs/daascore/:score[?count=10&prev=1] GET - /book/vspcs/bluescore/:score[?count=10&prev=1] GET - /book/blocks/:hash GET - /book/transactions/:txId GET - /book/addresses/:address/transactions[?daascore|bluescore=12345&count=10&prev=1] kaspad-API: GET - /kaspad/addresses/:address/balance GET - /kaspad/addresses/:address/utxos POST - /kaspad/transactions POST - /kaspad/transactions/rbf
English
2
15
56
1.3K
Aglovale retweetledi
NASA
NASA@NASA·
As communities gather this weekend, @AstroVicGlover reflects on the shared spaceship we all call home: Earth.
English
1.2K
8.2K
41.1K
2.2M
Aglovale retweetledi
Igra Labs
Igra Labs@Igra_Labs·
@Kaspa_KEF funded @eliottmea COB oracle research. @AppKaskad is now building it into production infrastructure for the entire Kaspa ecosystem, with the first deployment on Igra Netwotk. This is how ecosystems mature and scale, foundations fund research when outcomes are uncertain, and teams build then it into production because their protocols depend on it. More teams means more engineering hours, more capital, and more research that actually ships and make ecosystem stronger. Foundations plants the seed. The ecosystem grows the tree. We grateful to everyone in this chain.
Kaskad@AppKaskad

Indeed, the whole infrastructure of @eliottmea's COB oracle has already been built by @ColagrandePaul, and we're now integrating the model onchain for final testings. Once fully operational, the oracle will be available for the whole #Kaspa ecosystem ie Kasplex/Igra/Kaspa L1. We're thankful the @Kaspa_KEF was able to support Eliott in his research, and we're here to provide continuity for his work, acting like a lab environment with extra workforce to help him turn his research into applicable services for everyone, not just Kaskad. #researchandbuild

English
2
31
136
4.2K
Aglovale
Aglovale@aglovale0x·
@SWilliams471 @Igra_Labs Just setting the record clear. Been occupied with some RL issues & work commitments as of late. Still here in the background 😉.
English
0
0
1
50
Aglovale
Aglovale@aglovale0x·
Having a spine procedure in 2 days which will have me laid up for 12 weeks. Time to cook. Still mining $kas, holding $kas, and running rusty-kaspa nodes. Setting up an @Igra_Labs challenger node later this week, and other things 😉! 2026 is going to be spectacular for Kaspa!
English
12
9
79
1.7K
𐤊 Medaplor
𐤊 Medaplor@Medapl0r·
@aglovale0x @EbaratNeil @Igra_Labs For a second I thought you were a bitcoiner. I was like they don’t have spines. Why would they need a procedure on something that’s not there. You know it brother. Get well.
English
2
0
7
100
Aglovale
Aglovale@aglovale0x·
Would love to see a native stablecoin running on $kas rails; @Igra_Labs based L2 sequenced by Kaspa's L1 (PoW) would outperform & be more secure than any other option that currently exists. Tho I don't have much faith in native USDC; with $kas still not listed on @coinbase ...
Igra Labs@Igra_Labs

Loading…

English
2
13
76
2.7K
Nacho the 𐤊at
Nacho the 𐤊at@NachotheKat·
Kats are preparing for battles 🐾 9 realms. 9 civilizations. Which one is yours? Coming soon. $NACHO on $IGRA
Nacho the 𐤊at tweet media
English
5
23
80
2.4K