Solana Changelog: SIMD 16, Application Fees, and Sandstorm Hackathon

Welcome to the latest Solana Changelog, where we dive deep into the most recent developments and updates in the Solana ecosystem. In this edition, we're exploring some exciting proposals, new commits, and an upcoming hackathon that's set to ignite the Solana development community. Join us as we unpack the latest innovations that are shaping the future of this high-performance blockchain.

SIMD 16: A New Frontier for Application Fees

The Solana Improvement Document (SIMD) process continues to drive innovation within the ecosystem, and SIMD 16 is no exception. This proposal introduces a groundbreaking concept: application fees for writable accounts. But what does this mean for developers and users of the Solana blockchain?

SIMD 16 proposes a mechanism that allows decentralized applications (dApps) to set fees for writable accounts. In essence, this gives dApp developers more control over the economic model of their applications. Let's break down how this works and what it could mean for the Solana ecosystem.

Understanding Writable Accounts

Before we delve into the specifics of SIMD 16, it's crucial to understand what writable accounts are in the context of Solana. A writable account is any account that can be modified during a transaction. For example, if you have a token balance and you want to change it from one to two, you'd be interacting with a writable account.

The Mechanics of SIMD 16

SIMD 16 introduces a new program specifically designed for application fees. This program allows dApp owners to set fees for writable accounts within their applications. The key here is that the fee-setting authority lies with the program owner, not with individual users or validators.

Joe, one of the hosts, provides an excellent example to illustrate this concept:

"Say you have Orca trading on a market, people are trading on a specific market and that market's really hot. You can actually... Orca can change the fees for that market and make it higher or lower at their will so that they can kind of manage the user experience and how people trade on the market."

This level of control allows dApp developers to dynamically adjust fees based on market conditions, user behavior, or other relevant factors. It's a powerful tool that could potentially lead to more efficient and responsive dApps on the Solana network.

Centralization Concerns and Market Dynamics

While the ability for dApps to set their own fees offers significant advantages, it also raises questions about centralization. As Jacob points out:

"I feel like that sort of competes with the idea of having like more of a market-based fee setting, right? Like that's a little bit more of like an authoritative almost centralized way of doing things, wouldn't you say?"

This is indeed a valid concern. The proposal introduces a more centralized approach to fee-setting, which contrasts with the decentralized ethos that many blockchain projects strive for. However, it's important to note that this is still a proposal open for discussion and refinement.

SIMD 16 in the Context of Broader Fee Discussions

It's worth noting that SIMD 16 is not an isolated proposal. It's part of a broader conversation about fee structures on the Solana network. Joe mentions SIMD 4, which deals with changing base fees and fees based on computational costs. These proposals, taken together, represent a comprehensive approach to evolving Solana's economic model.

The Importance of Community Feedback

Both hosts emphasize the importance of community involvement in the SIMD process. Joe encourages listeners to weigh in on the proposal:

"I encourage anybody who wants to kind of like weigh in on that, go ahead, like that's part of the proposal process, you know, like we want public opinion, we want to have as many kind of like ideas flowing around and thoughts on different proposals."

This open approach to development is a hallmark of the Solana ecosystem and ensures that changes to the network are thoroughly vetted by the community before implementation.

Proof of Concept: Trying Out SIMD 16

For developers and curious community members, there's an opportunity to experience SIMD 16 firsthand. The creators of the proposal have provided a Proof of Concept (PoC) implementation. This allows interested parties to test the proposed changes and provide informed feedback.

Joe highlights the availability of this PoC:

"There's also the people that created it, they have a PoC. So you can actually try it out and see what it looks like for you and get the hands-on feel of it."

This hands-on approach to proposal evaluation is crucial for ensuring that any changes to the Solana network are thoroughly tested and understood before implementation.

Sandstorm Hackathon: Igniting Creativity in the Solana Ecosystem

While not directly related to network upgrades, the announcement of the Sandstorm hackathon is a significant event for the Solana developer community. This virtual hackathon, organized by Helius Labs and Lamport DAO, promises to be an exciting opportunity for developers to showcase their skills and build innovative projects on Solana.

Hackathon Details

Joe provides some key information about the event:

"It's called Sandstorm. And that runs from I believe January 10th to the 23rd. It's an online virtual hackathon. You can sign up with Lamport DAO and you can check out the site."

The hackathon features numerous sponsors and prizes, making it an attractive opportunity for developers looking to kick off the new year with exciting projects and potential rewards.

Community Support for Developers

Jacob emphasizes the supportive nature of the Solana community for developers participating in the hackathon:

"If you have questions on things when you're developing in this new hackathon, like feel free to ask them on either the Solana Stack Exchange and Discord, etc. Like, there's tons of people willing to help out."

This level of community support is a testament to the collaborative spirit within the Solana ecosystem and can be a significant factor in the success of events like Sandstorm.

Recent Commits: Enhancing Network Transparency and Performance

The Solana development team has been busy with several commits that aim to improve network transparency and performance. Let's take a closer look at some of these recent changes.

Counting Non-Vote Transactions

One of the significant commits mentioned in the changelog is a change to the way transactions are counted. Jacob explains:

"There was kind of a change to be able to count non-vote transactions, as well as vote transactions kind of separately in the bank. This kind of allows you to get a more realistic TPS via the get sampled performance RPC call."

This change provides a more accurate picture of network activity by distinguishing between different types of transactions. It allows for a more nuanced understanding of network performance and usage patterns.

Closed Accounts Visibility in Explorer

Another user-friendly update is the addition of closed account information to the Solana Explorer. Joe mentions:

"The closed accounts now appear on the Explorer, which, you know, is kind of cool. So you can see that account has been closed. You can get confirmation there."

This feature enhances transparency and makes it easier for users to track the status of accounts on the network.

Commission Changes and Validator Behavior

A particularly interesting commit addresses the issue of validator commission changes. Jacob explains the problem and the proposed solution:

"So what we were kind of seeing recently was that some validators were changing their commission rates at the last minute, which is not a great user experience. So in order to kind of like give time for users to react to maybe malicious validators changing their commission rates, their commission changes would be locked with this feature at the second half of the epoch, giving a decent amount of time for people to react if their validator is changing things."

This change aims to improve the user experience and increase trust in the validator ecosystem by making commission changes more transparent and giving users time to react to these changes.

Potential Impact on Validators

While this change offers clear benefits for users, it does introduce some limitations for validators. Jacob notes:

"I think it kind of like changes the way that you can change commission. Like if you can't change it as quickly in this, like you'll have to wait until the second half of the epoch is complete."

It's important to note that this change, while merged, still requires validator approval to be implemented on the network. This process ensures that all stakeholders have a say in significant changes to network operations.

The Broader Impact of These Changes

When taken together, these various proposals and commits represent a significant evolution in the Solana ecosystem. From giving dApps more control over their economic models to improving network transparency and user experience, these changes demonstrate Solana's commitment to continuous improvement and innovation.

Balancing Innovation and Stability

One of the challenges in blockchain development is balancing the need for innovation with the importance of network stability. The SIMD process, along with the careful consideration given to each commit, shows how the Solana ecosystem is navigating this balance.

Empowering Developers

Many of these changes, particularly SIMD 16 and the Sandstorm hackathon, are focused on empowering developers. By giving dApp creators more tools to manage their applications and providing opportunities for new developers to enter the ecosystem, Solana is fostering a vibrant and growing developer community.

Enhancing User Experience

From improved transaction counting to more transparent validator behavior, many of these updates are ultimately about improving the experience for end-users. As the blockchain space becomes more competitive, user experience will be a key differentiator, and Solana seems to be placing a strong emphasis on this aspect.

Looking Ahead: The Future of Solana

As we wrap up this changelog, it's clear that the Solana ecosystem is buzzing with activity. The hosts' enthusiasm is palpable, with Joe stating:

"Yeah, yeah, it's going to be a big year. You can already feel the sentiment. You know, I think the community is already coming back online. Everybody got a little bit of rest. So it's good to see and we will bring you guys more changes next week as per usual."

This optimism, coupled with the tangible progress we've seen in this changelog, paints a promising picture for Solana's future. As the network continues to evolve and improve, it's likely to attract more developers, users, and innovative projects.

The Importance of Community Engagement

Throughout the changelog, there's a recurring theme of community involvement. Whether it's providing feedback on SIMDs, participating in hackathons, or helping fellow developers, the Solana community plays a crucial role in the network's development and success.

Continuous Improvement

The regular nature of these changelogs, along with the ongoing SIMD process, demonstrates Solana's commitment to continuous improvement. This iterative approach to development allows the network to stay agile and responsive to the needs of its users and the broader blockchain ecosystem.

Conclusion: A Promising Start to the New Year

As we conclude this deep dive into the latest Solana changelog, it's clear that the ecosystem is off to a strong start in the new year. From innovative proposals like SIMD 16 to exciting events like the Sandstorm hackathon, there's no shortage of developments to keep an eye on.

The changes discussed in this changelog demonstrate Solana's commitment to improving every aspect of its ecosystem, from developer tools to user experience. As these proposals and commits move from ideas to implementation, they have the potential to significantly enhance Solana's capabilities and attract even more users and developers to the platform.

As always, the Solana community's active involvement will be crucial in shaping these changes and ensuring they meet the needs of all stakeholders. Whether you're a developer, a validator, or simply an interested observer, there are plenty of opportunities to get involved and contribute to the ongoing evolution of the Solana ecosystem.

Stay tuned for more updates, and remember to engage with the community, provide feedback on proposals, and perhaps even participate in the upcoming Sandstorm hackathon. The future of Solana is being built today, and everyone has a chance to be a part of it.

Facts + Figures

• SIMD 16 proposes application fees for writable accounts, allowing dApps to set fees for account modifications.
• A new program for application fees will be introduced as part of SIMD 16.
• The Sandstorm hackathon, organized by Helius Labs and Lamport DAO, runs from January 10th to 23rd, 2023.
• Recent commits include changes to count non-vote transactions separately, providing a more realistic TPS via the get sampled performance RPC call.
• Closed accounts now appear on the Solana Explorer, improving transparency.
• A new feature locks validator commission changes in the second half of an epoch to prevent last-minute alterations.
• The commission change feature requires validator approval before implementation.
• SIMD 4 proposes changes to base fees and fees based on computational costs.
• The Solana community is encouraged to provide feedback on SIMD proposals.
• A Proof of Concept (PoC) is available for testing SIMD 16.
• The Solana Stack Exchange and Discord are available for developers seeking assistance during the Sandstorm hackathon.
• The changes discussed aim to improve user experience, network transparency, and developer empowerment.
• The Solana ecosystem is showing signs of increased activity and optimism for the new year.

Questions Answered

What is SIMD 16?

SIMD 16 is a Solana Improvement Document proposal that introduces application fees for writable accounts. It allows dApp developers to set fees for account modifications within their applications, giving them more control over their economic models. This proposal aims to provide flexibility in managing user experience and market conditions within decentralized applications on the Solana network.

How does the new application fee program work?

The new application fee program proposed in SIMD 16 allows program owners (dApp developers) to set fees for writable accounts within their applications. This means that when users interact with a dApp and modify an account, the application can charge a fee determined by the dApp owner. This system gives developers more control over their application's economics and user experience, allowing them to adjust fees based on various factors such as market conditions or user behavior.

What is the Sandstorm hackathon?

The Sandstorm hackathon is an online virtual event organized by Helius Labs and Lamport DAO, running from January 10th to 23rd, 2023. It's an opportunity for developers to build innovative projects on the Solana blockchain, with numerous sponsors and prizes available. The hackathon aims to foster creativity and development within the Solana ecosystem, encouraging both new and experienced developers to showcase their skills and create exciting new applications.

How are non-vote transactions being counted in recent updates?

Recent commits to the Solana codebase have introduced changes to count non-vote transactions separately from vote transactions in the bank. This modification allows for a more accurate representation of network activity and provides a more realistic Transactions Per Second (TPS) metric via the get sampled performance RPC call. By distinguishing between different types of transactions, this update offers a clearer picture of actual user activity on the network.

What changes have been made regarding validator commission rates?

A recent update addresses the issue of validators changing their commission rates at the last minute. The new feature locks commission changes in the second half of an epoch, giving users more time to react to any alterations. This change aims to improve transparency and prevent potential exploitation by malicious validators. However, it's important to note that this feature still requires approval from validators before it can be implemented on the network.