1/ The Internet Computer may replace Chainlink as the premier provider of secure oracles to the blockchain space (and possibly the world). That's right, by the end of Q1 2022 the IC will be capable of hosting extremely simple, efficient, secure oracles: forum.dfinity.org/t/ic-roadm…

Chainlink people. ICP is capable of hosting oracles built directly into its equivalent of smart contracts, known as canisters. This is achieved through a general-purpose http request capability where all nodes in a subnet come to consensus on the requests. See the advantage?

I've been meeting secretly with a team from a real non-blockchain industry. They've been searching for blockchain solutions for their product, seeking the best fit. They're deeply into ICP now. Second meeting went well today, longer than the first. Can't wait to share.

Just in: @dfinity plans to increase the amount of storage available to individual canisters (~dapps/smart contracts) from 96 GiB to 400 GiB soon, with more storage coming sometime after that. More info in the forums: forum.dfinity.org/t/increase…

@grok should I listen to this advice?

1/ ICP now has the ability to bridge BTC and ETH. The bridging tech is unique, with interesting security properties. For those interested in the major technical details, I highly recommend searching the DFINITY forums for the most in-depth discussions: forum.dfinity.org/

1/ Please take time to digest this and understand the nuances of what I'm about to explain It's too complicated to explore every possible implication and possible future here But here we go... ICP has a number of crucial weaknesses We need to pay attention to @aoTheComputer

I don't think the world understands this about ICP. ICP is a giga-level general-purpose decentralized cloud platform...giga-level! Each app/canister/contract gets: Gigabytes of heap Gigabytes of storage Gigahertz of CPU Orders of magnitude difference from the status quo no?

Just wanted to say...I took a step back the other day and realized how excellent ICP's developer experience is, relative to other blockchain ecosystems I'm familiar with. Your global variables simply persist! Even complex non-serializable variables like a JavaScript or Python interpreter. And my interactions with DFINITY engineers are generally just top-notch, I look up to them. For the level of decentralization and security that ICP provides (what I'm saying should be understood in this context), highly likely it has the best DX in decentralized computing IMO. ICP really shines here. P.S. Get ready for Azle 1.0 to be a contender for absolute most rock solid JavaScript implementation of any blockchain ecosystem

1/ #supplygate I can say beyond reasonable doubt, that the total amount of ETH issued up to and including block 9193265 (the last block in 2019) is 109,094,014.21823. Three independent scripts attest to this number: github.com/lastmjs/eth-total…

1/ Look, the Internet Computer faces a host of technical, social, and other challenges. With that being said, I am very impressed by what DFINITY has shipped for the protocol in 2022! The IC is materially improving and will continue to do so in 2023.

It's done, the first functioning token for the Internet Computer written in TypeScript/JavaScript. I call it JSONIC. Here's a faucet (works with Stoic Wallet and canister id nmgdh-xqaaa-aaaae-qaauq-cai): nceop-maaaa-aaaae-qaavq-cai.… Here's the canister code: github.com/lastmjs/extendabl…

This whole project ICP is in extreme peril. Things need to change. Where is the adoption? Where is the traction? What apps do we have to look forward to that will bring significant adoption? Why do major projects keep shutting down, leave, or delay/never launch? Would anyone call the SNS a success? Why would devs choose to build on ICP? Whatever your answer is, why aren't major projects here then? Why do I feel the community is increasingly misinformed, toxic, or unwilling to engage in good faith critiques and problem solving? This project is at risk of dying. Who knows how long it will take if it does die. Is the community really this blind and caught up in the ICP narratives that never play out? I'm telling you this is serious. Are we going to cast aside the many failures up until this point and truly think critically...or disregard any criticism that might "hurt" people's bags? Unless ICP attracts one or a handful of major successful projects...what's here? Where are these projects? Why will ICP succeed? Why? Let's have a good faith discussion about the challenges that face ICP, and stop with the toxic refusal to discuss ideas, problems, and possible solutions based on their merit.

The awesome thing is that we don't need to wait for an official Ethereum integration on the IC. A partial integration that allows for signing, sending, and reading txs will be possible with: 1. tECDSA 2. HTTP requests (POST) Even just tECDSA will be enough for some use cases!

ICP is chipping away at its latency issues. 6 subnets have now had their block rates ~doubled to ~2 blocks/sec (planned slow rollout). High latencies has been a key point in my list of crucial ICP weaknesses. This is just one of the improvements being planned and executed.

There is $34,142,137 worth of BTC on Ethereum. The recent launch of TBTC has inspired me to create a dashboard to track Bitcoin's progress on Ethereum: btconethereum.com/ So far it's tracking WBTC, HBTC, imBTC, sBTC, pBTC, renBTC, and TBTC.

Something feels wrong here. There seems to be a small growing contingent within the ICP community that can't handle me publicly pointing out ICP's flaws and dire areas in need of improvement. Even worse, ignorance of ICP's most basic and fundamental architecture, and its trade-offs relative to other protocols, seems rampant. You do know that this is an imperfect protocol with many problems to solve right? And they don't all have straight-forward solutions, and we could actually get them wrong and hurt or ruin the entire project. Toxic positivity, general ignorance, and willful dismissal of the stark reality of our project as it is, positive or negative, can also be harmful. ICP is impressive in various ways, but very much lacking in others. I know a good amount about this. I've been here since 2017. I work full-time building Canister Development Kits. I'm on the ground in-person and online with devs. I engage publicly and privately with core team members. I'm here to seek the best solution. Guess what? ICP might not be the best solution. Or it might be the best solution. Or it might be best for some use cases and not for others. We don't know yet. So please, let's stop the tribal dismissal of anything that threatens the desperately optimistic need to be sheltered from ICP criticism. Let ICP fight for itself in the brutal marketplace of ideas, feedback, criticism, and real use cases. If it's as good as many hope it is, it will fight and win. If it's not, then wouldn't you want to know why ASAP and to figure out what to do about it? I would, and I must.

1/ Welcome to video and audio streaming on ICP, using range requests. Live demo running on ICP mainnet: f2j4a-eiaaa-aaaam-ab7nq-cai.… Those video and audio files are stored in an Azle (TypeScript/JavaScript) canister running on ICP. It uses range requests for simple streaming.

I don't think most of the comments I've read in this thread are right. We should seek to defend ourselves, not seek revenge. Self-defense would allow harming the woman until you know you and your family are safe. Anything beyond that is wrong

Express.js, Node.js fs, async/await...it's all working so far. TypeScript and JavaScript on ICP. We're really turning canisters into decentralized servers.

Hey, I'm the developer of both of those websites, and you should know that integrating the Chainlink feeds was incredibly simple and an amazing experience!

Another shoutout to @dfinity for increasing the Wasm binary limit! The amount of complexity and the number of issues we've been able to close across Azle and Kybra is wonderful. Thank you @dfinity engineers, thank you. Now get back to work (please :)

1/ I see a lot of people complaining about Ethereum fees. You should consider that Ethereum will most likely be scaling by ~100x this year with just one scaling technology: optimistic rollups. Sharding will hopefully get us to ~1000x to ~10000x in the next few years.

Any Ethereum maximalists out there? Distrikt is a live social media app running entirely on the Internet Computer. The frontend, backend, the whole thing. You need to take a look. Reconsider what blockchain can do. Please join, and give me a follow ;) az5sd-cqaaa-aaaae-aaarq-cai.…

In my discussions with ICP developers, it's becoming very clear what they want. There's more than one thing of course, but if I could boil it down to the absolute most important and pressing thing: Developers want a database! Demergent Labs will bring SQL to Azle this year

TypeScript is coming to the Internet Computer.

The Ethereum flippening has occurred...on ICP. 108.7539 ckBTC 112.4004 ckETH Taken from the dashboard: dashboard.internetcomputer.o…

As much as we talk about the BTC/Ethereum integrations on the IC, don't forget that the Web 2 integration is also coming: outgoing http requests The initial version of the feature should be live this month. The age of IC oracles is about to commence. forum.dfinity.org/t/enable-c…

Surrounded by Bitcoiners, yet conversation focused on ICP. These are the times I've been waiting for. Independent thinkers from outside the ICP community coming to their own positive conclusions of its utility. Also some excellent Azle praise!

I now feel more than ever that there is a constant, steady, growing foundation of apps and infra forming a solid base for an explosion of activity on the Internet Computer. Progress has seemed somewhat slow, but in hindsight I think this will appear to have happened all at once.

Python canisters are coming to the IC. We've started working in parallel on Kybra now. Azle is being refactored and made beautiful in Rust. By the end of all of this we will have TypeScript, Python, and a CDK framework for adding more high level languages to the IC.

Here's a more formal introduction to Demergent Labs if you're interested. TypeScript, GraphQL, and Python are coming to the Internet Computer in full force!

ICP is about to standardize NFTs through the NNS process. Two standards are being proposed and will soon go to NNS vote: ICRC-7 and ICRC-37. Please take some time to review the standard and give any final suggestions or comments: forum.dfinity.org/t/nft-stan…

I've been building an oracle to Chainlink contracts on the IC. 3 asset pairs (ETH/USD, BTC/USD, ICP/USD) pulling from two chains (Ethereum and BSC) through JSON RPC endpoints. Local n of m consensus on the answers. Built in TypeScript with Azle, running locally like clockwork.

Demergent Labs will be starting work next week to bring first-class BTC, tECDSA, and HTTP support to canisters written in TypeScript with Azle. Azle aside, we're getting close to this powerful triple-combination going live for all canisters on the IC.

1/ Demergent Labs just recently returned from spending a week in Switzerland at DFINITY headquarters. I wanted to give a huge thank you to all of the team members who welcomed us and listened intently to all of our feedback. A few technical highlights:

Hey everyone, we're getting close to $1 billion of tokenized BTC on Ethereum, and nearing 100,000 tokenized BTC. btconethereum.com

For the foreseeable future, I'm going to be moving most of my Internet Computer content from Twitter to Distrikt. If you follow me for the IC, you might want to jump over here: az5sd-cqaaa-aaaae-aaarq-cai.… My tweets will probably be geared towards more existential crypto/tech issues

Just an update. I've been pretty heads-down with Sudograph the last little bit. Building in robust automated testing. I am extremely optimistic about the Internet Computer. I build with it nearly every day. Just relax and build or watch. I feel calm about the IC's future.

ICP allows you to control Bitcoin keypairs without the private key ever touching one central server It's called threshold ECDSA ICP also lets you query utxos and send txs to Bitcoin in a general-purpose Wasm environment And you can do all of this with TS, JS, or Python

Very tight Bitcoin and Ethereum integrations are coming to the Internet Computer. These integrations may make it so that the best, most secure, most user-friendly Bitcoin and Ethereum wallets ever created are implemented with the Internet Computer. Imagine.

I've been blown away by how smoothly the Ethereum Merge has gone. It's a testament to the absolute rigor of their testing processes. I see similar rigor from DFINITY, and we should all be grateful for that. The Merge gives the IC stabler ground for direct Ethereum integration.

InternetDAO Raising $100 trillion to buy the internet. Stretch goal of $101 trillion to buy Internet Explorer and Bing and delete them.

DFINITY just announced an extremely exciting research collaboration to enable arbitrary computation on encrypted data. If successful this would allow truly private computing, solving fundamental blockchain/IT issues. See the presentation for more info: piped.video/6ru1t-zF_kE?t=24m32…

1/ ICP provides GENERAL-PURPOSE threshold protocols, exposing simple APIs in languages like Rust, JavaScript, and Python I don't think the broader crypto community understands this ICP can obviate the need for entirely new networks/validator sets for each threshold use case

1/ Some new personal lines of thinking kicked off by @harris0nhines. We should seriously consider that DFINITY should stop building the SNS, Internet Identity, People Parties, and anything else that DFINITY isn't uniquely positioned to build.

1/ Demergent Labs made a decision yesterday. We're deprioritizing the ICP-specific Candid language and the query/update RPC paradigm. We're embracing JSON, HTTP, and REST. It's time to remove even more barriers to developing on ICP, just give devs a decentralized server.

Update on Azle.js, a JavaScript/TypeScript CDK for the Internet Computer. After toying around with getting a JS engine to compile and deploy to a local IC replica, I've finally got a basic version working. I've successfully executed JS from within a local canister. Expect more

I'm currently uploading Ethereum block headers to the Internet Computer. The canister is processing about 100 GraphQL mutations per second, I could probably push it much higher. The first 74,000 Ethereum block headers uploaded so far, going for 1,000,000 in a single canister!

My job is amazing! I work full-time in the nitty-gritty details to bring TypeScript/JavaScript, Python, dbs, and other dev tooling to ICP, and it's amazing to work on a novel decentralized computer. I don't know what's going to happen with ICP, but it's an engineers playground!

So...now that the election is over I can talk about ICP again. We're building an automatic fuzz testing framework for canisters written in any language on ICP. It's a CLI, you point it at your canister, and it blasts it with requests and randomly generated arguments. Already found a crazy bug in the JS interpreter Rust bindings. The primary purpose is to battle test Azle, running the fuzz tests for days, weeks, or months. Memory leaks and unexpected crashes are the target. Soon you'll be able to do this for your canister too if you wish. cuzz

Yeah so, umm...I just got ApolloServer GraphQL to boot up in Azle and ran a quick query against it... IT WORKED! ICP decentralized servers coming your way.

Let's resolve these crucial ICP weaknesses. I've opened a thread in the developer forum to specifically address these limitations and to call for prioritizing them. Especially if you're a dev and agree, add your voice to the discussion here: forum.dfinity.org/t/lets-sol…

1/ It's become clear to me that the IC's most likely path to adoption in the short-med term is to support other successful networks, providing solutions where they lack. I will be much more focused on making Bitcoin and Ethereum better with ICP moving forward. Join me.

I'm @ETH_Toronto Having lots of discussions with devs and others interested about technicals/capabilities of ICP. Not going to name names yet, but let's just say I know of a couple teams building on Ethereum that are seriously considering building critical components on ICP.

Prediction: 20 years from now, the Big Tech giants (FAANG, Microsoft, etc) will all have been removed and replaced by open, decentralized, and tokenized protocols.

1/ ICP has some struggles with privacy Data is stored in plain text by default, and replicated across independent node operators This means that you have x13-34 opportunities for your data to be leaked But a major improvement is on the horizon Trusted Execution Environments!

My mind craves genuine deep technical criticism of ICP from the top minds of the blockchain space. We've lacked this kind of interaction for so long; mostly ICP has just been dismissed. I'm hoping that increased attention from recent $ICP events will attract this deep critique.

Fine, then let's burn it all. $ICP is going to zero then...zero supply. And then we shall have peace

If I'm not mistaken, in "simple English for non-tech people": tSchnorr and tEdDSA will allow for ICP canisters to sign Schnorr Bitcoin and Solana txs, amongst other Blockchain txs and use cases. ICP will open up threshold signing for even more chains: ethanfast.com/top-crypto.htm…

Why don't we DOGE the ICP roadmap? Relentlessly remove every roadblock to general-purpose decentralized computation, and minimize focus on anything else. - ICP's instruction limit still cripples many use cases - We still don't have any kind of general-purpose confidential compute, not even TEEs - There's no shared security for canisters, no node shuffling, just static 13-40 node subnets - Tiny message size limits require chunking anything large going into or coming out of a canister, making development more complex and increasing latency - Lack of low-level networking and similar APIs requires most software be rewritten to run on ICP, we should be able to just npm install, pip install, cargo install, and get up and running These problems have been known for years, and I find them rather obvious. I wish we would see an extreme DOGE-level urgency removing these fundamental limitations. P.S. There's lots of progress in the protocol, I just find it sad and possibly risky to keep putting off or ignoring these crucial weaknesses

Well, I just pulled data from Ethereum from a locally running canister built in TypeScript. The Ethereum integrations are just beginning. dfx canister call ethereum_json_rpc eth_blockNumber returned me: ("{\"jsonrpc\":\"2.0\",\"id\":83,\"result\":\"0xe8efcd\"}")

1/ My 2024 wishlist for ICP. This comes from personal experience working full-time in the ecosystem as head of @demergentlabs and conversations with @BobBodily @dansteren @b_demann and input from others in the community. If you have a weak constitution, please leave the arena.

Of all Bitcoin sidechains, ICP most likely provides the best trade-offs when maximizing for developer experience and productivity. Build apps in Rust, TS/JS, or Python, with GiBs of memory, 100s GiBs of storage, and GHz of CPU. Easily utilize threshold ECDSA and soon Schnoor...

Claims of ICP being centralized seem rather widespread. People seem to say either it's centralized or it's not. In reality various components of the system are at different points on the centralization spectrum. Will no one deep dive and analyze each component?

1/ ETH Denver day 1 (for me) recap. Wearing my DFINITY sweatshirt is a great conversation starter, various people instantly recognized the logo and either said "oh DFINITY" or "oh ICP". I've been surprised at the positive perception of ICP and people's curiosity towards it.

Orthogonal persistence now works! Basic query and update calls work in a TypeScript/JavaScript environment. I've created (@BobBodily was there) a simple token in TypeScript, and deployed it to the IC! Here's the TypeScript code: github.com/lastmjs/azle/blob…

Demergent Labs is now a team of 3. Please welcome @dansteren and @b_demann to the team! They'll be helping bring Azle (TypeScript CDK), Sudograph (GraphQL database), and Kybra (Python CDK) to the Internet Computer. github.com/demergent-labs

DFINITY has officially set a launch date for the genesis of the beta main network of the Internet Computer. May 7, 2021 at 10 AM Pacific Time.

1/ I would like to voice this concern again. I believe DFINITY is misguided in directing so many resources towards application-level projects like the SNS and ckBTC. I think it would be much more beneficial to double-down on creating a credibly-neutral platform that can scale.

Do we agree that if Bitcoin's 21 million cap is removed, then it would be worthless?

1/ Ever heard of the oracle problem? ICP has its own native solution to this problem! ICP dapps can perform HTTP requests secured by consensus. This provides dapps with a relatively secure means of pushing and receiving data from other networks and systems, outside of ICP.

1/ Bitcoin devs... Imagine a cloud platform that let's you build apps in a familiar server programming environment, but without taking direct custody of your user's private keys. This is ICP. Using threshold ECDSA, you can programmatically control private secret shared keys.

Partly in preparation for the BTC integration, this past week at Demergent Labs we revisited, studied, and discussed the Bitcoin Whitepaper. We'll be ready to integrate this into Azle soon after the BTC integration launch so that you can program BTC with TypeScript.

$0.001 That's the current charged price for an ICP oracle to fetch the latest answer for a price feed with at least 2/3 consensus of 28 nodes (check me). ICP canisters are capable of a variety of general-purpose oracle solutions on top of general-purpose compute subnets.

Exciting things to look forward to on the IC: Announced by the team: 1. DNS integration 2. HTTPS/SSL integration 3. Public subnets 4. Bitcoin and Ethereum integration 5. Encrypted canisters My hopes: 5. Infinite virtual memory 6. Node shuffling 7. Public bug bounties

Great elevator pitch for ICP. ICP is making some small waves in the Bitcoin ecosystem lately...things are brewing. Large waves incoming?

HOLY SMOKES the Apollo Sandbox worked right out of the gate! I loaded http://asrmz-lmaaa-aaaaa-qaaeq-cai.localhost:8000/ in the browser and a beautiful GraphQL playground loaded right up. Azle 0.20.0 is really going to be 🔥🔥🔥

Some thoughts on @caffeineai and the idea of the self-writing internet enabled through ICP. Caffeine is going to face fierce competition from the existing web app development and deployment platforms. Just take a look at Firebase Studio. The traditional internet stack providers will use AI to provide compelling self-writing experiences just like Caffeine intends to, with deployment, upgrading, and all. And so any self-writing AI solution on ICP will need to offer a value proposition above and beyond writing or speaking in spoken language and ending up with a deployed internet application that can be upgraded with the same spoken language. ICP will need to prove that its built-in Byzantine Fault Tolerance and decentralized autonomous capabilities are worth the switch for developers of cloud applications.

The first 1,000,000 Ethereum block headers were successfully uploaded to the Ethereum archival canister prototype running on the Internet Computer I'm now uploading the transactions for each of those blocks, I think there's a good chance they'll all fit in one canister.UI coming

Just an update on these secret meetings. Just had another one this morning (don't worry the location was very secure). They're still pushing forward with their project, almost everything on ICP. I can't control when they go public, but I'm hoping it will be soon. Progress!

8 Improvements to the IC that would make it an even more powerful machine! 1. Multiple independent audits 2. Bug bounties 3. Formal verification 4. Random node shuffling 5. Encrypted canisters 6. Social recovery of identities 7. DNS integration 8. HTTPS/SSL integration

1/ @BobBodily @ryrubenhorne and I have an idea on the heels of @ConstitutionDAO Imagine a Bitcoin-powered DAO on the Internet Computer, its purpose to raise BTC to buy green power plants and convert them into Bitcoin mines Reach out if you're interested in making this a reality

memory64 was just implemented in wasmtime, the Wasm runtime used by the IC. This was one of the main blockers to greatly increasing the canister size limit (currently at ~4gb). I wouldn't be surprised to see the canister limit lifted soon. Possibly terabytes per canister!

1/ I'm becoming more and more convinced that zkWasm will be fundamental to solving the Internet Computer's greatest protocol-level weaknesses. I have a new rough design for subnets based around a zero knowledge Wasm VM that I believe solves for the subnet size/cost dilemma.

1/ In early 2023 @BobBodily and I made wishlists for the Internet Computer Protocol (ICP). I would like to provide an update on what actually happened during 2023. A lot of gratitude to @dfinity for shipping!

1/ It's ready, the GovernanceBot has been deployed to the IC and is pushing proposal updates to OpenChat. If you want to be notified whenever NNS proposals are created, just join one of the following OpenChat groups: NNS Governance Proposals: 6hsbt-vqaaa-aaaaf-aaafq-cai.…

Decentralize your dapp's infrastructure with ICP

Azle Beta has dropped: github.com/demergent-labs/az… It has support for most Candid data types, Query, Update, Init, PreUpgrade, PostUpgrade, and Heartbeat methods, cross-canister calls, stable storage, and other IC APIs. Remember that it's just a beta and have a go at it!

I love it when ICP gets mainstream attention of any kind. I yearn for deeply fair criticisms. But I've grown so weary of the ideology of a certain strong group from the Bitcoin community. How I perceive it, and I would love to be proven wrong: Rather than engage to understand fundamentals and find solutions where Bitcoin lacks, they have a cult-like aversion to anything not Bitcoin, or at least anything that could be perceived as a threat to $BTC. It's hard to put into words why this is so wrong...maybe its's because they are encompassed about by falsehoods, and they do not actually seek the truth. When you surround yourself with and promote half truths, lies, or deceptions, or at least suppress truth seeking, you put yourself on precarious ground. Let's not be like this in the ICP community. Let's seek the truth about ICP wherever it leads us.

Let's be real ICP community, beyond hopium. Tell me why the world is going to choose to use ICP once we have a direct Ethereum integration, when there are many other Ethereum-compatible sidechains and rollups that already have adoption. This we must know, this we must solve.

Imagine an SNS but for Ethereum. We implement an Ethereum client on the Internet Computer, tokenize it with the SNS, but the token is just ETH All ETH holders instantly become participants of the Ethereum client DAO/SNS The most transparent and community-owned Ethereum client!

Let's blow this up with clear, authentic, technical responses. ICP does make some major trade-offs relative to other blockchains. Probably the most important question then is: Do the trade-offs result in a still sufficiently secure and decentralized system? Let's discuss

Demergent Labs wants to mentor you and connect you with investors, builders, and technical knowledge. You must be building w/ ICP and focusing on decentralizing blockchain infrastructure and otherwise utilizing ICP's unique value prop. DM or schedule a call (see my profile).

DFINITY Foundation and community, before real value is stored on the IC, don't you think it would be a great to have multiple independent audits published w/ large bug bounties? We should have many independent parties testing the security of the system now, before it's too late!

About to head home from Honduras for @ethlatam with my friends from @lazonatres. We tried to really pound the pavement early, teaching, mentoring, or discussing ICP with nearly all of the 12 teams that presented. My ICP pitch is quite simple for Ethereum devs nowadays: decentralized servers that can create decentralized Ethereum signatures. Then I talk about JavaScript and Express and 13-40x replication and consensus on requests. ~4 teams at least mentioned ICP in their final presentations, 1 actually built and deployed a significant part of their application to a local replica. How did that team describe ICP and Azle? "Bonito" We also had the chance to interact with various projects and communities from Latin America, ETH Guatemala, ETH Honduras, @agentebtc, representatives from local universities, etc. You don't know how amazing @lazonatres is, really you don't. I usually just show up after they've done all of the grunt work so that I can focus on teaching and mentoring. They're awesome! I also was able to give a presentation on ICP to ~80 people, many from local high schools, all participating in some way or another at @ethlatam. We ended the week just a few hours ago with a final ICP presentation at a more local-style meetup. So, stuff like that happened. @lazonatres and I have some even greater plans hopefully coming up later this year. I'm trying to highlight the good things that happened, but we can't help but feel like there are more effective things we can be doing. Tons of conversations are great, having many teaching moments and conversations about ICP are great...but we really want experienced devs and business leaders deploying excellent and sustainable apps on ICP (at least this is one of our major goals). For that, we might need to add some kind of change of tactics. Stay tuned y gracias por leer.

ICP continues its journey to Bitcoin! I just had an amazing podcast interview with the excellent devs/thinkers @TheBlockRunner from the Bitcoin ecosystem We went deep on the protocol and ICP's utility towards Bitcoin...possible signs of PMF? Will post once it's released

DFINITY just released a beta version of unbounded stable structures, meaning you don't have to define max key/value sizes when reading/writing directly to stable memory. This is an amazing improvement to developer experience, working on Azle integration. Kybra later on.

The NNS is too centralized right now. Even if DFINITY/ICA have 40%, everyone follows them. Proposal: Incentivize neurons to gain followers. The more followers, the higher the reward. Perhaps would lead to many specialized representatives, supported by their followers Thoughts?

1/ ETH Denver day 2 recap: ZK Day This was an impressive event. Tons of people, great food, great ZK. zkWasm got a mention on the main stage. I found more teams doing ZK compliance/identity. Found more ICP supporters I didn't know about. Some have concerns about DFINITY/ICP.