OpenAccess

Preparing for the Future. Stay Tuned.

[OpenAccess @openaccessX]

2025 Status Update:
One year of quiet is enduring for curious minds so a status update is more than appropriate.
After a lot of coding and twice as many creative breaks as well as study & research in the past year, our current work is focused on the underlying infrastructure & hardware. Even creating a new purpose-built kernel was explored (fyi: Linux = Kernel). While worth it, this might become a future project, for the sake of time-to-market. So for now, stepping in the footsteps of every other company is the best option (most rely on Linux or, like macOS, are built upon FreeBSD). Nevertheless, the current infrastructure work guarantees a future-proof & stable foundation, which is being achieved closer any day.

With reliable architecture, our first service will be merged with revision to have a best-in-class foundation, necessary to achieve actual goals beyond. If the time of 2026 allows for it, the next post will be a public invite to stress-test & exploit (bug bounty) the system. Who knows, perhaps a smart mind can do it & be rewarded for it. This will also be the time to present our vision to financial backers, sponsors (e.g. foundations) or investors, which will in turn decide the structure of our endeavor (NPO, Collective, Foundation, Corp/AG/S.à r.l., DAO or else). It's seen as a duty to at least offer the opportunity to become an early part of this.

Some of our core principles:
• "Stay stubbornly independent” - as life teaches, many things or ideas like to get stolen or bought, only to be messed up afterward.
• “High-quality groundwork” - instead of over-engineered, copy-paste layering.
• “Global advantage” - instead of profit for a few.
• “Do it for the best” - ignore the rest.

As the pendulum swings, in all situations, keep your head up, touch some grass, sand or snow, enjoy winter/Christmas time & a Happy New Year.

[OpenAccess @openaccessX]

Stay tuned and don't worry, we'll loop back around to continue previously mentioned endeavors.

[OpenAccess @openaccessX]

@nustleo @kadena_io i see what you did there 😗

[OpenAccess @openaccessX]

@CryptosR_Us Time.. to work out of boredom, passion, and purpose!😄

[OpenAccess @openaccessX]

@Randynamic_4 I remember you exploring/working on a load balancer using gas as a metric back in the day - rementioned in the 0033 pull request. I think it was set aside due to consensus, but it's still a long-awaited improvement. 🫤

[OpenAccess @openaccessX]

Looks like that was categorized as a reply instead of a post.
https://t.co/HwrmAGECUA

[OpenAccess @openaccessX]

@kadena_io #Kadena
Added KIPs that we believe are vital and beneficial for everyone, and we hope to see them implemented sooner rather than later in some form.

0033: Not much we can do on our end for this.
0034: Helpful for planning to know if the #WebRTC proposal is being picked up.
#Blockchain #P2P #Decentralization

https://t.co/kbJ4xhcRq6

[OpenAccess @openaccessX]

@kadena_io @KeyPerspective there you go :)

[OpenAccess @openaccessX]

@kadena_io #Kadena
Added KIPs that we believe are vital and beneficial for everyone, and we hope to see them implemented sooner rather than later in some form.

0033: Not much we can do on our end for this.
0034: Helpful for planning to know if the #WebRTC proposal is being picked up.
#Blockchain #P2P #Decentralization

https://t.co/kbJ4xhcRq6

[OpenAccess @openaccessX]

@1Answers 😄 Keep preaching.
As long as they keep adding even more improvements, we’ll get there!

[OpenAccess @openaccessX]

Always surprising how unforeseen challenges and delays lead to quality improvements.

While working on the wallet, significant enhancements to Blockstorage have been made:

• Storage space requirements decreased by ~65%
• Resulting in ~65% fewer transactions, faster uploads, and cost reductions!
Leading to more sustainability, competitiveness, and happy end-users. 🌱💪😊

Stay tuned for more updates!

#Blockchain #Storage #Sustainability #TechInnovation #CostReduction #Kadena

[OpenAccess @openaccessX]

@ron_kda @C4Cryptos @amir @Hank_Cjr @KadenaBharat Isn’t Amir in the BD team?
Note: The BD question was meant for him; my mistake.

[OpenAccess @openaccessX]

Thank you for your question. There is absolutely no connection between our team and the old or current Docushield teams.

In fact, I personally considered exploring a storage solution about two years ago. Interestingly, the very next day, Docushield appeared on Ryan Matta's show. Our initial reaction was, "This can be better, but it's not finished yet." So, we decided to give them time to complete their product and then evaluate its effectiveness. Meanwhile, we focused on other projects and came up with several new ideas to explore.

About a year ago, we started with a wallet project and transitioned to a dapp at the beginning of 2024. This journey taught us a lot about the development hurdles that we, or any other developers, shouldn't have to overcome repeatedly for each new project.

We have now tackled the more complex part of transaction management for handling numerous transactions with large sizes at a local level. This solution can be reused and offered to many other projects, though different kinds of projects will have their own unique challenges to address.

Rest assured, we have no affiliation with any other project on Kadena. We were just as disappointed as everyone else to see Docushield abandon their project, investors, and the ecosystem.

[OpenAccess @openaccessX]

Announcement

History: Initially, we started developing a wallet intended to make everyone's life easier. In the midst of it, the focus shifted to an application with the recognition that another wallet wouldn't bring much initial value to the #Kadena ecosystem, leading to the sentiment of "Oh, not another wallet."
--
While we finished our first project (aside from a few promotional images), the only wallet (@eckoWALLET ) capable of handling our transaction volume and sizes, though with significant impact on user experience, announced their departure.

This means we are delaying the launch of our first application to finish and integrate an early access version of our own wallet. We're a bit regretful that we won't be able to provide the planned fully-fledged wallet version at its launch, but it will offer features others don't.

Should anything change regarding this wallet situation in the meantime, we'll reevaluate.

To show our appreciation and ensure you don't go empty-handed, we're gladly providing a quick preview. Due to the added workload, it's not as 'shiny' as we'd like it to be for a first introduction, but we hope you enjoy it.

#openaccess #blockstorage #directpay

[OpenAccess @openaccessX]

@linx_labs We appreciate @LinxWallet, @koalawallet, Chainweaver, and Ecko - each has its uniqueness and works like a charm with any existing dapp. The first two especially stand out with their modern look, all beautifully designed.

Didn't say that either. 😉

[OpenAccess @openaccessX]

@linx_labs For various reasons, including the fact that Linx Wallet isn't available on PC yet, we decided not to use it. A proper local wallet can actually be defined as the user themselves.

[OpenAccess @openaccessX]

"though with significant impact on user experience"
🙁

[OpenAccess @openaccessX]

@OneHitta9 @AmirDapl That’s possible, but given the current sentiment and the number of users switching wallets, it doesn’t make much sense to force users onto a discontinued wallet. There are also other reasons for this decision.

[OpenAccess @openaccessX]

Thank you for your interest.

- User + Wallet = 2 Parties.
- Wallet Tracking: Whether a wallet tracks user activity can be verified by examining its code or network connections.
- Data Access: Accessing data from a public blockchain involves more than just providing it for free.
- Potential Solutions: Technologies like Zero-Knowledge Proofs (ZK) may address these challenges.
- Previous Posts: In an earlier post (sneak-peak video), the number of full Quicksign transactions required can be seen. As a user, I understand that this could be frustrating.
- Custom Solutions: We have various reasons for needing a custom solution to address future needs effectively.

[OpenAccess @openaccessX]

@hodl_pepe The statement refers to 'No subscribtion based Pinning-Services'

[OpenAccess @openaccessX]

@linx_labs We require native Quicksign. Using WalletConnect involves third-party infrastructure and detailed user tracking, which contradicts our commitment to providing the best service, including strong privacy protection