Can you build at the speed of__? On November 15th, during the Devcon event, we started the #Build with OS journey together at the Workshop in Bangkok with this question in mind.
In the opening speech, Chief Innovative Officer Jason gave a keynote speech entitled "Build onchain, any chain". He focused on the multi-chain characteristics of the OS platform. Its wide ecological coverage can provide developers with support for more than 100 different blockchain networks (including Ethereum, Bitcoin, Solana, etc.), helping them seize emerging opportunities and enter the market faster. 
Regarding the product details, OS BD director Shen introduced on the spot: Currently, OS provides 4 types of powerful APIs, including Marketplace, Explorer API, etc. Taking the OKLink browser API as an example, Explorer and EaaS provide rich developer tools, 50+ mainstream blockchains (including EVM, UTXO chain and Solana's on-chain data), and token data of 200+ networks. Developers can access real-time on-chain data, summary statistics and seamless contract verification through browsers and other APIs. Easily integrate EVM RPC modules for smooth migration and high compatibility .
The EaaS service can help development teams fully tap the potential of blockchain exploration. Whether it is a new L1 or an established chain, rollup or application chain, our zero-cost service can be tailored to your specific needs.
During the forum, Simon, Product Director of OKLink , initiated a discussion on the theme of " What is the new gold mine of blockchain data " from the perspective of data infrastructure. Guests from Blocknative , Rootdata , Consensys SMG , Amberdata and Blockaid shared their insights from both theoretical and practical perspectives.
Q
Simon@OKLink : What are the most pressing issues or challenges in bringing Web2 users to Web3? Security issues, trust issues, difficulty in finding "gems" among the many new projects? Or the technical complexity of existing tool experience? How can blockchain data solve the above problems? What plans/projects are currently trying to solve (or have solved) these problems?
A
Raz@Blockaid : In my opinion, user experience and security are the issues that need to be paid attention to first. For example, can your grandmother get started with the product you are making right away? So make sure your users can fully understand what you are doing and what benefits it can bring to them. We can see that many projects and applications in the industry are already doing very well. If a Web2 user can fully understand the login interface when logging into a Web3 application without spending a lot of extra time, and the prompts on your interface can make them believe and let down their guard that it is safe, then this sense of boundary will naturally disappear, and introducing Web2 users will no longer be a bottleneck that is difficult to break through.
A
Matt@Blocknative : My answer may be different from everyone else's. I think users need to have a good reason to come to the chain . I want to ask each of you, do you remember the last time you solved your payment problem on your phone, why did you do it? For me, I came to Thailand for the first time two weeks ago, and I needed to use the transportation app Grab, so I downloaded it. When I was in Chiang Mai, I couldn't use a credit card, so I downloaded another payment app. In such a scenario, there is a clear signal to remind me that hey you really need cash. This is a very convincing scenario. In such a situation, it is not surprising why users make a clear choice.
Do you still remember the first time you logged on to the Internet? There was only one Internet. But when you come to the on-chain world, you have multiple network choices, and the complexity is significantly increased. For example, user experience, rates, and latency are all issues you need to think about. In my experience, the most convincing scenario is: Telegram robots. It is not free, but it is very convenient to use and very simple to set up. It only takes a few clicks to get results, so users will be satisfied with it. So my point is that this kind of user experience means that we should do our best to avoid the complexity and do useful things . Useful things may be entertaining, interesting, or practical, but they must be useful.
Q
Simon@OKLink : For institutions or enterprises interested in entering Web3, what challenges will hinder their adoption of Web3 technology? How can blockchain data help them accelerate the adoption of Web3 technology? Examples are welcome.
A
Hunter@Rootdata : I would like to take the example of the project I am working on, Rootdata. It may be different from other guests. We are a Web3 asset data platform focusing on off-chain data. We have become a data platform necessary for investment decisions of millions of Web3 users, and we are also committed to becoming a productivity-level tool for Web3 enthusiasts and investors. By presenting more refined data, including physical addresses, financing rounds, etc., we help project owners and senior people make better decisions. The rapid changes in the entire industry drive us to use data means to continue to move forward.
Q
Simon@OKLink : Change seems to be the norm for Web3, with new chains emerging every week. It is extremely challenging for Web3 builders to iterate on the right use cases while dealing with the evolving chain infrastructure (which currently seems to be multi-chain coexistence). What innovative data tools can separate infrastructure from user experience and enable Web3 builders to quickly test ideas and incubate the next killer application?
A
Tongtong@Amberdata : I have been working in data-related fields for 7 years and have gone through several cycles. It feels like people have not paid attention to data itself for a long time. But now it is different. In several events I have attended, I am very excited that the participants are discussing which data indicators they are paying attention to, and letting these data "madmen" and "magics" share insights in the community, which reflects that each of us is trying to understand the data and connect them. Therefore, the data tools represented by APIs provided in the market can solve the problems of developers, because powerful APIs make it no longer a problem to obtain data, and it is processed in an aggregated way in one stop.
A
Max@Consensys SMG : As we build new chains, we may face the problem that as more integrations are added, the value of the chain itself gradually becomes lower and lower, which can easily lead to the loss of developers in the ecosystem, and the maintenance cost remains high. Developers naturally need a series of toolkits, so from my point of view, there should be enough efficient and easy-to-use toolkits on the chain to facilitate developers to quickly get started and integrate conveniently, so as to continue to maintain the competitive advantage of the new chain.
At the same time, we had a dialogue with many developers on the spot about data productivity tools. Among them, Master Cui Mian ( @MasterCui ) , an opinion leader in the developer community and a special researcher at the Science and Technology Innovation Research Institute, shared his experience from the perspective of a senior developer and technical lecturer: "The on-chain data and analysis platform can help developers build smart. On the one hand, it can carry part of the backend work, and the data it provides saves the cost of developing a backend to obtain data. Another possibility is that the on-chain data platform itself can be repackaged into a new application. For example, I can apply the results of the ready-made data to other applications I have developed."
In addition, he said that communication and efficiency are very important in the development process. Mature on-chain tools can greatly save the development team time in finding corresponding open source code and provide good statistical and collection tools. Therefore, developers should make full use of all available APIs and other data tools, and use AI and other means to continuously optimize development collaboration, improve efficiency, and maintain innovation and competitiveness in the Web3 field. 
Talking about the challenges encountered during the development process, developer Panda ( @CodeMorePanda ) said: "Because the entire public chain ecosystem is very diverse and heterogeneous, for example, the ecosystems of Solana and EVM are completely different. If we connect them one by one ourselves, it will be a waste of time. At this time, we can actually choose some data aggregation APIs , such as the OKLink API we are using, which can greatly reduce our development time, focus more on our own time, and save energy to be creative." 👉https://www.oklink.com/zh-hans/api-plans
Build Onchain, Any Chain . We had a pleasant afternoon talking freely with developers in the relaxed workshop. The pace of building the on-chain ecosystem has never stopped. As data tools become more sophisticated and AI methods become more intelligent, more creativity and inspiration will continue to emerge, and will also drive Web3 to bring more unexpected excitement in a smarter and more agile manner.
