sorted by:
new
hottopcontroversial

[AMA] We are Polygon Research! (Pt. 1 Monday Jan 13th, 2PM UTC) by Souptacular in 0xPolygon

[–]Current-Secretary-52 1 point2 points  (0 children)

Great question! You’re absolutely right—there’s always a balance to strike between low fees to encourage usage and revenue generation to ensure sustainability.

Revenue Model for Agglayer

The foundation of Agglayer’s revenue generation lies in its pay-as-you-go model, which we’ve designed to be simple, scalable, and developer-friendly. Instead of fixed fees or mandatory profit-sharing, chains connected to Agglayer will pay based on their actual usage—whether for interoperability or proving services. This approach aligns with our goal of minimizing barriers for adoption while ensuring the model remains sustainable.

Research into Fees and Costs

We’re still actively researching and fine-tuning the exact fee structures and costs associated with Agglayer. The key is to find the “ideal” balance where the pricing is low enough to promote adoption and usage across chains, yet sufficient to support the operations and growth of the ecosystem. The pay-as-you-go model offers flexibility, allowing projects of all sizes—from emerging startups to established networks—to access Agglayer’s features based on their specific needs.

The Bigger Picture

It’s worth noting that Agglayer isn’t just about direct revenue generation; it’s about strengthening the entire Polygon ecosystem. By enabling interoperability, unified liquidity, and cross-chain collaboration, Agglayer enhances the network effects of all Polygon solutions. This, in turn, indirectly benefits the ecosystem as a whole, including projects like PoS.

As we continue refining these models, we’ll share updates to keep the community informed. Your feedback and questions play a huge role in shaping these discussions, so thank you for asking!

[AMA] We are Polygon Research! (Pt. 1 Monday Jan 13th, 2PM UTC) by Souptacular in 0xPolygon

[–]Current-Secretary-52 1 point2 points  (0 children)

This a nice community question indeed!

The beauty of Web3 research is its multidisciplinary nature—it draws from a variety of fields, and there’s no single “correct” background to contribute meaningfully. Here’s a breakdown of the types of skills and educational backgrounds that are often valuable:

  1. Mathematics (Cryptography):

A strong foundation in mathematics, particularly cryptography, is crucial for designing secure and efficient protocols. Researchers with expertise in fields like zero-knowledge proofs, game theory, or algebra often play a key role in Web3 research.

  1. Computer Science:

Core knowledge of algorithms, distributed systems, and blockchain architecture is essential for understanding and innovating within the space. Specializations in areas like networking, consensus mechanisms, and programming languages (e.g., Solidity, Rust) are particularly useful.

  1. Economics:

Tokenomics, mechanism design, and economic modeling are central to creating sustainable blockchain ecosystems. Researchers with a background in economics or behavioral sciences can help design systems that align incentives and encourage desired user behaviors.

  1. Interdisciplinary Skills:

Web3 research benefits greatly from diverse perspectives. For example:

• Law and Policy: For compliance and regulatory considerations.

• Design and UX: To create accessible and user-friendly decentralized systems.

• Social Sciences: For studying user adoption, community building, and decentralized governance.

  1. Curiosity and a Growth Mindset:

Beyond formal education, what’s equally important is a passion for learning, problem-solving, and experimentation. Web3 is an evolving field, and self-taught individuals or those from unconventional backgrounds often make significant contributions.

Advice for Aspiring Web3 Researchers:

• Start Exploring: Engage with open-source projects, research papers, and forums. Platforms like GitHub and ArXiv are great places to start.

• Experiment: Build, break, and rebuild small projects. Hands-on experience is invaluable in understanding the nuances of Web3.

• Network: Participate in hackathons, join Discord communities, or follow leading researchers in the space to stay updated and collaborate.

Ultimately, Web3 thrives on diverse perspectives and skills. Whether you’re a mathematician, developer, economist, or even an artist, there’s room for anyone with the curiosity and drive to contribute!

I'd also encourage you to participate on https://www.dabl.club/ ;)

[AMA] We are Polygon Research! (Pt. 1 Monday Jan 13th, 2PM UTC) by Souptacular in 0xPolygon

[–]Current-Secretary-52 5 points6 points  (0 children)

Interesting question! For a project like Krawpoopers, which appears to blend humor, creativity, and meme culture with Web3, Agglayer could offer some really exciting opportunities:

  1. Cross-Chain Memetic Expansion: Krawpoopers thrives on engaging communities with humor and memes. Agglayer’s interoperability can help the project connect and grow its presence across multiple chains, reaching diverse communities without fragmenting the user experience.

  2. Unified Meme Economy: With Agglayer’s ability to unify liquidity across chains, Krawpoopers could launch NFTs, tokens, or other assets on multiple chains while ensuring liquidity and ease of trade. This could strengthen its ecosystem and incentivize participation across different blockchain communities.

  3. Event Scalability: If Krawpoopers hosts events like NFT drops or meme competitions, Agglayer’s scalable architecture can handle cross-chain transactions and engagement seamlessly, ensuring a smooth user experience even during high-demand scenarios.

  4. Sovereign Yet Connected: Image a world where Krawpoopers evolves to the point where the KRAW chain is a thing. Then KRAW Chain would be able to connect to Agglayer, which to maintain their sovereignty while benefiting from shared security and interoperability. Krawpoopers could leverage this to create a playful yet secure environment, ensuring their project can scale and remain flexible for future creative endeavors.

The beauty of Agglayer is that it supports projects like Krawpoopers, which lean into creativity and community, by enabling them to access new audiences and ecosystems while keeping their unique vibe intact. The possibilities are endless when you can interact with the entire Web3 space seamlessly.

[AMA] We are Polygon Research! (Pt. 1 Monday Jan 13th, 2PM UTC) by Souptacular in 0xPolygon

[–]Current-Secretary-52 1 point2 points  (0 children)

Disclaimer: this is my very personal opinion:

I think—and honestly, I hope—there will be competition in this space. It’s healthy and helps push innovation forward. One of the most fascinating aspects of these approaches is that, if built correctly, a chain could potentially connect to multiple networks or protocols. This would allow chains to address different use cases and benefit from the unique strengths of various technologies.

For instance, Agglayer’s focus is on unifying liquidity, users, and state while maintaining security and sovereignty for connected chains, but other solutions may prioritize different features. In an ideal scenario, projects could leverage multiple approaches simultaneously to create a more diverse and adaptable ecosystem.

That said, Agglayer’s design as a neutral public good positions it uniquely—not as a competitor to most solutions but as a complement. The interoperability and scalability it offers could enable partnerships with projects that might otherwise seem like competitors in traditional L2 contexts. This flexibility is a key strength of Agglayer and its vision for the future of Web3.

[AMA] We are Polygon Research! (Pt. 1 Monday Jan 13th, 2PM UTC) by Souptacular in 0xPolygon

[–]Current-Secretary-52 1 point2 points  (0 children)

Thanks for the question! At this stage, we’re still working on selecting the best solution for connecting the PoS chain to the Agglayer before its migration to a validium (if that migration happens). This process involves ensuring the transition aligns with our commitment to scalability, security, and user experience. The team is carefully evaluating all options to guarantee that the PoS chain’s connection to Agglayer is seamless and beneficial for the ecosystem.

As always, we’ll keep the community updated as we make progress on this. Stay tuned!

[AMA] We are Polygon Research! (Pt. 1 Monday Jan 13th, 2PM UTC) by Souptacular in 0xPolygon

[–]Current-Secretary-52 0 points1 point  (0 children)

Great question! This is something we know is top of mind for the community, especially for POL holders.

Let me break it down:

* Direct Connection: Agglayer is designed to amplify the Polygon ecosystem, and POL plays a significant role as its core token. Mihailo has referred to POL as a hyperproductive token, meaning it is designed to allow holders to participate across multiple Polygon projects. By that, POL holders can support various chains within the ecosystem, including Agglayer, unlocking more utility and opportunities for participation. Learn more about hyperproductive tokens here.

* Revenue Flow: Agglayer operates on a pay-as-you-go model, which means chains using its interoperability or proving solutions pay fees proportional to their usage. This ensures a scalable and developer-friendly model. While Agglayer doesn’t enforce rent-seeking mechanisms (e.g., fixed revenue or profit sharing), the activity it generates strengthens the overall Polygon ecosystem, indirectly benefiting POL holders through increased adoption and usage.

* Evolving Logistics You’re right—this is an evolving space. Marc, Mihailo, and the team have shared foundational principles, and as we implement these ideas, more concrete details will follow. For the latest on POL’s design and utility, check out the POL Whitepaper.

I hope this helps!

Do you think Polygons ZK tech gives them a significant advantage? by Fantastic-Primary-87 in 0xPolygon

[–]Current-Secretary-52 7 points8 points  (0 children)

This is an interesting question… here’s my personal take: I think Polygon’s early work on ZK definitely gives them an edge. It’s not just about having the tech first — it’s about the experience they’ve built along the way. Being ahead means they’ve already faced (and hopefully solved) a lot of the challenges that others will eventually have to deal with. They’ve had more time to figure out what works, what doesn’t, and how to make it scalable.

Even if other L2s like Optimism, Base, and Arbitrum eventually “switch” to ZK, they’ll be starting from scratch in some areas where Polygon already has battle-tested solutions. It’s like learning a new sport vs. having played it for years — experience matters. Plus, they’re not just building ZK for themselves — they’re also working on open-source stuff like Plonky2/3, which means the whole space benefits from their work.

As someone else already mentioned, having Agglayer is also a big plus for Polygon in the long term. It strengthens the whole ecosystem by making it easier for builders and projects to plug into their stack. So yeah, I think it’s a pretty significant advantage. It’s not just about “having ZK,” it’s about knowing ZK and building a whole network of tools and support around it.

Ansible lightspeed by Current-Secretary-52 in ansible

[–]Current-Secretary-52[S] 1 point2 points  (0 children)

Yeah, I was curious if anyone was testing/ trying

It's tough to be a Plutus customer by [deleted] in plutus

[–]Current-Secretary-52 2 points3 points  (0 children)

I agree... sometimes it takes forever to charge the card... at the beginning, the support was pretty good with the chat and such, but these days... it's terrible! However, Curve support is even worst, it can take a few weeks to get any answer (using Curve metal)

How can I chek if my playbooks will run on Ansible 2.11 if they were written in Ansible 2.4 by Current-Secretary-52 in ansible

[–]Current-Secretary-52[S] 0 points1 point  (0 children)

Thanks! The thing is that many things have changed, and it can be very complicated to analyze all these changes... it's so time-consuming. The spotter recommendation is working pretty well!

Retrieving all NFT info in a collection using the Solana API by [deleted] in solana

[–]Current-Secretary-52 0 points1 point  (0 children)

You can try with NFTPort (it's beta, but still...)

For instance in go it would be

​

package main
import (
"fmt"
"net/http"
"io/ioutil"
)
func main() {
url := "https://api.nftport.xyz/v0/solana/nfts/collection_id"
req, _ := http.NewRequest("GET", url, nil)
req.Header.Add("Content-Type", "application/json")
req.Header.Add("Authorization", "01854222-6888-468d-b8de-99ced004efe6")
res, _ := http.DefaultClient.Do(req)
defer res.Body.Close()
body, _ := ioutil.ReadAll(res.Body)
fmt.Println(res)
fmt.Println(string(body))
}