Oleh Andrushko @olichdev

@MetaWin 😍

@MetaWin a4bc9585

@MetaWin a4bc9585

📝 A new article on how to securely #encrypt the #data using a #wallet🚀 Process implemented inside Formana platform on @solana #blockchain. 👉 olich.me/post/formanas-…

💣 Just submitted my final MVP project for MasterZ x @solana Bootcamp. 👉 Learn more and check it out: formana.olich.me #Solana #Blockchain #MVP #Forms

📝 My new article on indexing #blockchain and #ipfs data using @graphprotocol 🚀 👉 olich.me/post/indexing-…

Oleh Andrushko is on GitRoll! Click on the link below to check out their profile. gitroll.io/profile/uiMY2h… #GitRoll

We recently released Foundry Upgrades, a plugin that simplifies secure deployment and management of upgradeable smart contracts from Foundry. 🚀 Deploy upgradeable contracts with less lines of code 🔍 Upgrade contracts with storage collision checks ✨ Use Defender to deploy deterministically and safely across chains 🌈 Support for Transparent, UUPS, and Beacon proxies github.com/OpenZeppelin/o…

JavaScript Runtime Service Use Cases One of the many examples of how the JavaScript runtime can be leveraged: Edge Functions Fleek Network’s core development team built an Edge Function use case on top of the JS runtime. It allows developers to execute serverless JavaScript functions that are edge-optimized. It also supports a wide variety of Web APIs that developers can import into their functions and build unique apps with. In preliminary testing Edge Functions on Fleek Network were 7x faster than AWS Lambda and 2.7x faster than Vercel serverless functions. Explore the results in more detail here: blog.fleek.network/post/fleek-net…

FLK Whale @FLKwhale

2 years ago

Early POC of JS Runtime Service ⚡ Built on top of Fleek Network by the core development team, v0 of the JS Runtime POC uses IPFS as its origin, caching the functions around the network, and Fleek Network's Handshake component for highly performant JS function execution. Since

2 5 20 5K 4

blog.fleek.network/post/fleek-net…

Our goal is to build the best Solidity organization in the world at Coinbase. We're very early days. We recently started codifying our style, development, and testing guidelines and are sharing here github.com/coinbase/solid…. A v0.01 with lots to improve!

📝My new article on #solidity smart contract development with #foundry. A detailed guide covering everything you need to know from how to work with foundry to configuring a proper CI pipeline 🚀 👉 olich.me/post/smart-con… #Blockchain #Ethereum #SmartContracts #GitHub #Web3

👉 Setting up a complete and fully operational repository for @solidity_lang smart contract development using @HardhatHQ, @biomejs, solhint (by @protofire), husky and slither (by @trailofbits). { by @olichdev } from @hashnode hashnode.olich.me/setting-up-sma…

⚡ Whitepaper tl;dr {1}: Background ⚡ Feedback from the release of the new paper has been great! To make the info more accessible we're starting a TLDR thread series on the key aspects of the protocol Starting with some background: what drives need for an edge network in Web3?

⚡ New Edge Platform Whitepaper & Repo ⚡ Today we are very excited to release the new whitepaper and open source repo for Fleek Network’s decentralized edge platform. whitepaper.fleek.network

⚡️ How Content Addressing Gives FN an Edge ⚡️ Content addressing might give Fleek Network several advantages over traditional edge platforms/CDN’s. Let's dive into all the performance, data integrity and availability benefits it could enable. blog.fleek.network/post/how-conte…

By enabling any developer or team to build their own recommendation algorithm, the combination of easier to leverage AI primitives, open protocols, and immutable public data are paving the way for a more personalized and superior user experience (UX) for social applications. With apps like Twitter, TikTok, and Instagram people are stuck with the given recommendation algorithm without any choices or options other than leave the platform if they don't like it. For instance a lot of changes have happened with the Twitter recommendation algorithm. People have complained that they see a lot more clickbait, but the only other option is just the "Following" feed or to leave. In theory, because web3 and blockchain data is public, developers and teams could build their own recommendation algorithms. I said "in theory" because in the past this was not really a thing as this type of system did not really exist before. We're now starting to see some great alternative recommendation algorithms emerge and become available in the @LensProtocol ecosystem, and apps are already starting to pick them up! Here are a few teams working on this from various angles (not inclusive of all teams): 1. @karma3labs - Is a ranking and reputation infrastructure using the EigenTrust algorithm. It enables developers to curate a ranking and recommendation system for their apps based on on-chain data. karma3labs.com 2. @whitebox_build from @0xbasedalex - an open protocol to consume, develop and collaborate on modular, composable, and transparent algorithms, owned by the developers. I think of this as something like an NPM for recommendation algorithms whitebox.build 3. @madfiprotocol - creating various recommendation algorithms like a suggested follows API + "For You" API and enabling optionally financial mechanisms allowing users to boost themselves creators.madfinance.xyz We have a handful more that are also available or being worked on. Watch this space! It is one of the key differentiators between private, proprietary, and sometimes predatory social networks of the past, and modern social platforms like @LensProtocol

keyboard_arrow_left Previous keyboard_arrow_right Next

@pierreminik Supabase is used as SQL database in this case. All the data tracked by Umami are stored in Supabase.

@Pauline_Cx @umami_software @vercel @supabase 🏗 A simple guide to achive that: olich.me/post/self-host…

🌠 Community Picks Self-hosted analytics platform with @umami_software, Supabase, and @Vercel: hashnode.olich.me/self-hosted-an… By @olichdev.