I'll be talking about the @ORIGYNTech NFT during an ama on the Origyn discord channel: discord.gg/g7xcGTrh 11:30AM Pacific on Wednesday.
2
1,667
341
1/ Tonight I did a Smart Pier transaction between @dfinity's #IC and #Polygon's Mumbai Testnet.
8
50
192
Prediction: In 3 years 50% of circulating $BTC will be held by #IC smart canisters and on-chain smart wallets. It all starts next week with the t-ecdsa rollout.
16
33
169
We are going to move the value to the edges. No more CEX. No more DEX. You. Your the bank. You transact with others directly. No middle man. No value capture. You get the whole value. WEX. Wallet exchange. Your code. Your data. Your always on personal internet computer. Nothing in the middle between you and what you want to accomplish except pipes and safe, verifiable code. #IC
15
27
132
7,786
The joy in a developers face when they realize they can deploy the full stack of their web app to the #IC blockchain is so fun to watch. Selling them to come do the work isn’t hard after that. We just need to get the word out. #SuperNova
26
114
I would highly suggest that the @dfinity employee responsible for this be awarded many gold stars and employee of the month. Please step forward so you can take your bow.🙏
10
18
108
6,094
I wanted to take a quick moment to thank @dfinity for the amazing work in putting on the storage and scalability ICP.lab. The future of the IC is bright and some of the coming features are going to be face-melting. :).
5
20
100
4,553
ICRC-3! It has be amazing working with some very smart people on a number of standards to make the #IC go over the last few months. You can go vote now to approve ICRC-3: dashboard.internetcomputer.o… So what is ICRC-3? 👇
3
21
99
3,941
I read the Arweave ao spec so you don't have to (ao.arweave.dev/). I posted my thoughts over on taggr.link/#/post/677509. #EthDenver #Arweave #InternetComputer
4
29
94
19,440
Hey @EthereumDenver, @ORIGYNTech will be at the @dfinity booth today and tomorrow showing off our multi-library, 48GB-on-chain, data permissioned, serves https(yes video), market on the inside, royalty preserving super NFT that powers our certificate of authenticity platform. 👋
1
17
77
9,677
Infu and @anvil_ic have quietly built some of the most important and ingenious pieces of IC infrastructure. The stuff the guy has queued up to build is amazing. Fully funding him to build on the IC is a 100x move that will have implications far beyond the value of any one token. Plant trees you don't get to sit under.
7
28
85
6,126
This is a bit bittersweet for me as the OGY Governance canister was the first 'real' contract I wrote for the IC. It launched a full year before the SNS-1 test was run and has served us well for two and a half years. There are still a few things it does really well (Let voters change their vote after following neurons vote...🤔🔍...) that I'm proud of, but it is going to be a big relief to hand over the responsibility of making governance better to the SNS team who has the time and mission to build amazing DAO software so that the Origyn team can focus 100% on delivering the value the platform promises. 🚀🚀🚀
IMPORTANT ANNOUNCEMENT📢 We will be upgrading $OGY to the Service Nervous System (SNS) on the $ICP. This is marking a major evolution in our DAO's framework. This shift enhances our role as a neutral, universal certification standard for #RWA . Full details on our medium article: medium.com/@ORIGYN-Foundatio…
6
11
88
5,067
The @gldrwa DAO is funded! What does it mean for @ORIGYNTech? Our tech will be at the core of the largest marketplace-built-in gold market on the planet. Always on, Always for sale, Data-Rich, Transparent Inventory. All of that and you'll be able seamlessly switch physical gold for gold-backed fungies.
5
16
85
3,053
I'm on TV!
Tune in to this week's ICP Talks featuring Origyn! Join @aisconnolly as she chats with @afat from @ORIGYNTech about the latest in multichain technology. Discover industry trends, future aspirations, and how Origyn leverages Chain Fusion. Watch here 👇 piped.video/watch?v=KLElm8cq…
5
6
94
3,315
Alexander's 'Sofware eats the world' talk.OOPLSA '96.Years before @pmarca said it. The most impt software talk ever? piped.video/98LdFA-_zfA
1
31
85
Pretty excited about this opportunity! finance.yahoo.com/news/tradi…
1
14
71
4,000
I posted a response and set of opinions over at tagger: Part 1: taggr.link/#/post/957824 Part 2: taggr.link/post/957837 This is a response to @lastmjs 's concerns about the limitations of the #IC in light of @aoTheComputer . I'm not going to try to tweetstorm it. I'll reply with some highlights and images, but head over there if you are interested.
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
2
20
74
10,628
Did you know that the @ORIGYNTech NFT has a permissioned database inside each NFT? You can give dapps space to keep track of things in your NFT(ie. game state, ownership records, chats...any data really) I walk through the basics here: piped.video/rjeJJj_a38w
2
13
43
It is always fun to see hard work make it into production. Congrats to @dfinity and everyone who participated in the ICRC Token Standard working group. Let's approve some transfers. :). dashboard.internetcomputer.o… . .
3
15
70
2,344
The $OGY token for @ORIGYNTech is now ICRC-1 compliant. It should now work with all your ICRC-1-related tools. All the legacy IC Ledger functions are still there as well.
4
13
60
7,622
Now we are cooking! viewblock.io/arweave/tx/V675… Maybe the first @arweave ANS-104 compliant DataItem signed trustlessly by and broadcast from the #InternetComputer. Cost was about $0.013 cent with the test ecdsa key. Prod key would be 3x. @ao cu next!
2
16
67
4,397
Hi #ETHDenver2024! I'll be giving a short presentation about the #IntenetComputer 's ICRC 1/2/3 standards, the working group that put them together, and how you can use them to build Fungies on the IC! Stop by the @dfinity booth at 11:30!
1
15
61
2,213
Version 0.1.5 of the @ORIGYNTech NFT is now live: github.com/ORIGYN-SA/origyn_… It includes some cool new features such as: - A new, simpler #ask type for creating new sales - Canister Notifications of New Sales - Dutch Auctions - The ICRC7 draft interface
19
66
3,973
1/ I’d like to share the culmination of many months of building and laser focus here at @ORIGYNTech . This is a major milestone on our journey to implement a multi-year vision to protect authenticity and appropriately reward human creativity and ingenuity. medium.com/@ORIGYN-Foundatio…
1
10
30
Async programming on the #IC has a lot of dark corners and things to consider. If you are looking to launch something, reach out, I may be able to provide an audit(for Motoko contracts) or friendly advice. 👀
5
17
57
3,269
1/3 Pretty amazing day yesterday for an #InternetComputer geek. Rapping about the things coming from @ORIGYNTech, hearing about @yulinliu20’s new project, spending hours with @timothanke talking about motoko and #IC best practices, and then an amazing dinner with @dominic_w.
2
6
62
The nice thing about going #8yeargang with your #ICP stack is that on days like today you can just keep coding and scrounge for change in the couch to build the stack.
2
3
62
1/n Hello #IC family. Today is my 45th birthday and I’m running a fundraiser for ICDevs. Since I’ve now crossed into old man territory I have 12 spicy hot “man yelling at clouds” hot takes to relay
11
13
56
How did #supernova go for you? Work on a cool project, learns a lot, but maybe it doesn’t have legs? @ORIGYNTech is hiring and we’d love to meet teams that already know how to execute together. We are building infrastructure for the next generation of web apps on the #IC.
1
12
60
After a number of weeks of reorganization and couple of years worth of experience, I've published four ICRCs for the NFT WG to consider next. Ledger Markets, File Systems, Static and Dynamic Metadata. More info over at the forum forum.dfinity.org/t/nft-work…. Come join the WG!
4
14
58
3,150
#chainfusionsummer Can't wait to deliver what we have in the pipeline.
4
6
59
4,123
The IC got super lucky that Current Gen AI is so neatly separated into training and running the trained model. We'll be able to run trusted models on the IC signed by keys that no human can have. I think AGI will need recursion which will likely require massive online accelerated compute which isn't realistic for the IC, but at one point I think most of us probably thought even step one would require massive compute to simulate intelligence.
7
50
2,272
This should be funded by now. Come on ICP peeps. Cash the meme-coins and fund real infrastructure. The stuff @lightning_lad91 has been working on has implications across the multi-chain-universe.
Hey #ICP fam 👋 It’s been 24 hours since the Funded campaign for Nucleus went live and y’all have helped me raise 250+ ICP. I can’t tell you how much your support means to me. Thank you 🙏 We have 29 days left in our campaign and I will be taking full advantage of that time to communicate why I think we need this capability on the #InternetComputer. funded.app/projects/motley-4…
5
14
51
3,444
I've been know to say that one of the top 10 things the IC community could do to advance the ecosystem is to get @lightning_lad91 to spend all his time on the IC. Make it happen and get an NFT. Use @funded_app and help reach the goal funded.app/projects/motley-4…
3
16
47
1,587
I’m super excited to participate in the Motoko Bootcamp! dfinitycommunity.com/motoko-… This 100% free event will help beginners and experience devs bootstrap into the motoko language and launch you into the world of developing for the #InternetComputer
10
49
Wen #DeFi on #IC? Now. nitter.app/ORIGYNTech/status/1531…. It has been a long road, and yes, we're working on better standards, but all the tools to make defi work are there now.
ORIGYN is one of the longest standing projects on the #InternetComputer. Sonic is a premiere #DEX on the #IC. It’s high time for a mashup. The $OGY utility token from @ORIGYNTech is now live on @sonic_ooo! Check out medium.com/@ORIGYN-Foundatio… for the full announcement. @dfinity
1
6
52
Sweet! @TaggrNetwork sent me $.06 worth of #icp for posting about #ICDevs on their social media platform that runs completely on the #InternetComputer. I ❤️ these experiments! 6qfxa-ryaaa-aaaai-qbhsq-cai.… Social media that we own is the future.
10
48
Here is a summary of my discussion on telegram with the @WaterNeuron team yesterday. I learned a lot. I still have concerns. I make suggestions. The discussion between @afat , @sisyphusdancing , and leo revolves around the WaterNeuron (WTN) and its governance within the context of Internet Computer Protocol (ICP) and Network Nervous System (NNS). Here's a detailed breakdown of the conversation, including the nuances of opinions and solutions provided: 1. 51% Attack and Governance Afat's Security Concerns: - Afat raises the issue of a 51% attack, wondering what prevents a malicious actor from taking control of the neurons by acquiring a majority of WTN. Leo and Enzo's Responses: - Leo explains that the neuron canister is NNS controlled, not SNS controled, which inherently protects against such attacks. The NNS has mechanisms in place to ensure security. - Enzo elaborates that the NNS controls the canister and the protocol, thus preventing unauthorized upgrades or attacks. 2. Role of NNS and SNS Afat's Inquiry: - Afat questions why the SNS is necessary if the NNS can control the utility canisters directly, suggesting it might be simpler to deploy utility canisters without the additional layer of SNS. Leo and Enzo's Explanation: - Leo explains that the SNS adds a layer of bootstrap and voting, which introduces game theory and helps attract participation and investment. - Afat insists on the team explaining that value in more detail to justify why it needs to be an SNS. 3. Governance Mechanics and Voting Afat's Concerns: - Afat delves into how votes are mirrored and the potential for errors in governance if votes are not handled properly. He asks about the impact of wait-for-quiet mechanisms and the specifics of how voting outcomes are determined. Leo and Enzo's Details: - Enzo explains that they do not care about proposal approval itself but rather the voting trend one hour before the NNS expiration. This approach minimizes errors and aligns with the governance structure. 4. Team Allocation and Vesting Afat's Concerns: - Afat worries about the team allocation of tokens and the risk of team members leaving after receiving their tokens and if the size is justified given the straightforwardness of the code and the simple perpetual motion mechanic. He suggests the need for mechanisms that ensure long-term commitment and accountability and some value delivery after launch. Leo and Enzo's Assurance: - Leo assures that there are vesting mechanisms in place, with tokens being locked for at least a year and then distributed over time. This ensures that team members are incentivized to stick around and contribute to the project's success. - Austin notes that the SNS does not have a recovery mechanism and the only penalty is making team allocation members wait. 5. Technical and Philosophical Concerns Afat's Philosophical Concerns: - Afat raises concerns about riskless staking and its potential to incentivize poor governance participation. He questions how to maintain the integrity of NNS voting and avoid governance problems. Leo and Enzo's Perspective: - Enzo acknowledges that many voters vote without understanding, primarily to gain rewards. They stress the importance of building tools and verifying releases to improve the quality of governance. - Afat loves that his is service provided and wants more of that. If the team is going to provide a robust set of replica and canister validation services, this is the kind of value that justifies some team allocation. 6. Future Strategies and Improvements Afat's Proposal: - Afat suggests that if WTN hits certain limits, the DAO should cap and fork, with the team allocation being halved with each split. This would create competition among the new DAOs and ensure continuous improvement. (This makes the team payout logarithmic instead of unbounded. The team can still pick a limit that delivers incredible wealth.)
7
5
45
2,658
A bunch of work went into this release. Thanks to the whole ORIGYN Team for their support, patience, and effort!
#ORIGYN is excited to introduce the next evolution of its #tokenomics and governance model with the launch of ORIGYN Tokenomics 3.0 💥 Discover more : medium.com/@ORIGYN-Foundatio…
2
3
45
1,877
We have an rc for the @ORIGYNTech NFT that fixes the range request issue from last week. We'll get it deployed and then @dfinity can turn back on video and audio streaming. Thanks for the patience!
3
7
48
1,559
ao has a point here about the state being consistent if the log is played ⏩ from genesis. The IC has a general assumption that the crypto lets you discard state. But with ICRC-3 it is easy NOT to discard state and get this 'holographic' piece as well. dashboard.internetcomputer.o…
Holographic state is a key innovation used in ao that enables boundless scalability for decentralized compute. Instead of coming to consensus about the state of computation itself, ao ensures logs of interactions are stored on Arweave, creating a 'hologram' of the state. 👇
1
7
47
4,263
Popping up from a self-imposed x break: My talk from this year's @icp_cc was released today. You can hear me talk ICP Maximalism, give my take of NFTs on bitcoin, cover @ORIGYNTech is working on, and give some suggestions on what I think devs should be working on. Preview: The ETH chain doesn't know you are using tecdsa + ICP -> port protocols. Back to work. A bunch more over the next couple of weeks.
2
11
45
1,544
This card is pretty sick. Scan with your phone, plug in your gmail, and get a canister wallet on the IC that can hold ckBTC, matic....I'm guessing eth as well? Should I plug these into axon?
4
5
44
4,092
Does anyone want to fund a Motoko EVM? Does anyone want to build a Motoko EVM? It's time.
1/x We are live! @gitcoin #GG20. We've joined the Web3 Infrastructure round and we're raising funds to extend our evm project beyond just opcodes. You can donate today and the round will be open for 14 days. 👇
3
10
46
2,766
I'm super excited to be headed to @EthereumDenver. I'll be spending plenty of time at the @dfinity booth talking about all things @origyn, @pan_industrial , ICRC-1,2,3,4,7,8,16,37,56 and beyond. Stop by to say hi if you're going. mailchi.mp/internetcomputer/…
1
12
44
2,486
If you are curious how big the fud squid is, people are porn bombing our #IC #DEFI dev zooms like it is mid-2020 Jr. High Math class. 😂
5
1
40
I logged into @OpenChat from an "add to Home Screen" today and it asked if I wanted to enable notifications. Just now I got a notification from a web app. This is huge for IC dapps! Anyone have a pointer to the spec?
3
4
42
2,166
H/t to @theUSERGEEK for achieving this technically since it was possible. BUT this is the biggest existential threat to the IC. I doesn't matter that "there is enough VP out there that this doesn't matters" Black swans and the sands of time are real. I think we should consider that these neurons shold be identified and blacklisted to set a precedent. The ability to lockdown neurons as non transferable should be enhanced. Transfer should only happen for purposeful reasons. We tried raising this as a discussion point last year: forum.dfinity.org/t/proposal… If these markers emerge we have to completely change the security model of the IC or it WILL eventually be used to attack the network. The NNS will need to go away In its current incarnation. At a minimum the debate about this needs to be seriously escalated and risks assessed.
Great news!🚨 We are launching #IDgeek today! It is a secure, automated and decentralized marketplace for #InternetIdentity Anchors with their linked assets. All transactions are executed entirely by smart contracts on #InternetComputer. Check it out 👉 idgeek.app
11
7
43
11,200
Boom!
Huge improvements are coming to #Motoko in 2024! 👀No longer needed to serialize and deserialize your stable variables across canister upgrades. 🎉 See all the updates just around the corner github.com/dfinity/motoko/pu…
3
6
43
2,189
Fun day outlining the @ORIGYNTech NFT tech release roadmap. Can’t wait to build this stuff. We are hiring #IC devs. Immediate need for a Sr. Rust dev and any Sr. devs wanting to learn #motoko.
7
45
It is just maddening. What am I missing? nitter.app/VitalikButerin/status/… #the_IC_already_does_that I fixed the image. #IC #ICP
3
14
38
Almost have v0.1.0 of the @ORIGYNTech NFT ready for the auditors. Working on the release notes.
1
7
36
If listing a token in a bear market is cool then we're Miles Davis. Let's go @ORIGYNTech 🚀🚀🚀 #OGY #ICP
2
3
40
Must have!!!!
My new favorite shirt just arrived! Kudos to @afat for the coming up with the tagline! You can get yours at the Austin ICPCC Meetup: lu.ma/w0fu0z2k #ICPCC2024 #ICP #InternetComputer
2
2
42
1,393
If you want something like this where the assets are on chain and you can compute over content of the dapp, @ORIGYNTech nft 0.1.2 supports hosting an entire dapp, http addressable inside an NFT on #IC. Feel free to mint ownership to your dao. Sell via built in nft marketplace.
Today, we're introducing something exciting: Non-Fungible Apps (NFAs) A new approach for on-chain tokenization of apps that will help unlock better decentralization, censorship resistance, and community ownership for Web3 frontends. 🧵 blog.fleek.co/posts/introduc…
3
6
36
3,870
Replying to @dominic_w
Sovereign Digital Objects. It's in global-uploads.webflow.com/6…
1
8
38
1,740
What every your estimate of the percentage of web3 that will be running on the #IC in three years, you're probably off by two orders of magnitude. These tech demos they are showing are wild. Coming soon: Public Monthly Updates. Can't wait!
1
3
36
1/ Want to go deeper into the @ORIGYNTech NFT? In this video(piped.video/watch?v=am7ldqaw…) I look at the migration system and the types inside the NFT. It is a bit wonky because I was also trying to convert the code to kusangi, but I've tried to edit all of that out.
1
6
14
Deploy solidity smart contracts to the Internet computer with hard hat. docs.bitfinity.network $0.02 transaction fees.
1
8
40
3,404
If you are interested in Pub/Sub and events on the #InternetComputer, please come to our Working Group today. forum.dfinity.org/t/technica…
2
12
40
3,848
Anyone remember whisper? We do and we'll be discussing how to bring it to the #IC in our working group on Wednesday at 7PM CET. forum.dfinity.org/t/technica… 👇Vitalik in 2014
2
7
40
1,950
I've completed the audit for the NTN DAO's DeFi Vectors code. It is quite a lovely piece of software and I learned a lot doing the audit. There are some really interesting mechanisms here and I'm excited to see how people use it. Link in reply.
2
3
38
2,035
Well. I can write and sign an ANS104 data item from motoko now. That was pretttttty miserable. You need sha256, sha384, keccak(but don't forget get the invisible space), zigzag ints, vints, and a custom hash structure. Whether or not an arweave bundler will take it wil have to wait for tomorrow. #ao from the #ic? Maybe.
1
7
37
1,758
I'm super excited to be teaching about the native HTTP interface and certified content for the #InternetComputer at #MotokoBootcamp. My lesson is in 10 minutes! dfinitycommunity.com/motoko-…
2
3
37
1/ @ORIGYNTech kicked off the sale of its first NFTs today on the @Impossible_NFT marketplace. impossiblethings.com/nftforg… You can buy the digital jersey of either @ivanrakitic or @ELS_9_FRANCE and the proceeds benefit the @UEFA_Foundation .
2
12
37
I hit a bit of a stumble in my quest to deploy an @aoTheComputer MU, SU, and CU on the #InternetComputer. It seems that transactions that write messages to arweave use RSA signatures and the IC can currently only do ECDSA trustlessly. I found a bundler at @ardriveapp that I thought was going to work, but they only honor RSA on the data items as well. So until I can find a bundler that will accept ECDSA signed data items I’m stuck with: 1. Uploading the RSA key into the canister, but that could get exposed to boundary nodes and canister hosts, or 2. Use an off-chain relay for the transaction which exposes the key to whoever is doing the relay and keeps it from being a self-contained unit. This is provided I can actually sign a data item with ecdsa which I haven’t confirmed yet. I'll keep investigating.
9
4
38
3,542
Sorry for the mega post, but I'm a bit out of time to day and wanted to get this out. Today was an interesting morning. The YC @CigDao_ has been going through some growing pains and in an attempt to stabilize some things we’ve had a number of serious proposals lately that have been very lightly voted on. This is due to the fact that you have to burn your tokens to vote. A cool feature in most scenarios, but with the small size of the dao and the significant size of changes I’ve been looking for easy ways to implement non-burnable voting so we can get a better view on what the DAO wants. I had some code I was considering and went to check out the core contract. As a developer is want to do, you mess around. The temptation to click mint(dashboard.internetcomputer.o…) just to see what happens is always there and as light indulgence, I jammed in a 1 with a bunch of 0s and hit mint. This is not supposed to work. But it did. And now I’m in a conundrum. Someone is going to notice this issue very soon and the ramifications are going to be unpredictable. One of the biggest things that saved ETH in the early days was the quick thinking during the DAO and the withdrawal by white hats of significant tokens that allowed the hack to be minimized. In that same spirit, I started doing all I could to remove as much ‘capturable’ value as possible before someone else saw a very unexpected mint and went to try it themselves. It appeared the mint was at least gated by a max supply so I probed this limit to get up to the max. I wasn’t sure what to do next, but feared a panic would lead to significant selling. In hindsight perhaps my decision wasn’t the best, but after poking around it looked like the only liquidity pool was on sonic. I had minted 273 Billion YC, which I think was like over 25% of the supply and I was hoping that I could get all the ICP out. And then any fallout would be fixable on the YC canister side. The 273 B didn’t go as far as I expected and I was only able to get most of the ICP out. A few users bought up some cheap YC and we may need to figure out what to do there as it may have supply issues. I tried a few more things to see if I could get the rest of the ICP out but I was just competing against myself and couldn’t mint any more YC as the bug was tapped out. At this point, I contacted the current and previous leaders of CigDAO(@ALLiDoizCode , @Nihilor2 , and @accumulatingicp ) to start mitigation of the issue and get it fixed. We also knew the code had been used elsewhere so we did some penetration testing on STACKED and OLD @icsneed and confirmed they did not have the same vulnerability. At this point, all the ICP has been returned to the CIGDAO treasury and the bug has been patched. I’ll let the contract author give a better description as to what and why the bug was there. The couple of hanging threads are what to do about any fees generated by my massive trade on Sonic(if anything can be done) and what to do about the excess YC that may be out there as a few people bought up cheap YC that shouldn’t exist. I’ll leave that up to the DAO leadership to work through. This begs a number of questions. What should we do about these kinds of vulnerabilities on the IC? Auditing is hella expensive (I do audits on the IC if you need one) and since we have upgradeable contracts, audits need to be evergreen. This is even more expensive. When canisters change we need to know. This bug isn’t in the YC codebase that I could find and I expect that it was a one off change for a governance issue, but am not sure. Can we ensure somehow that code doesn’t get deployed that doesn’t have public code? On the Motoko side we’d need a motoko compiler on the IC that can check with GitHub on hashes. Azel might actually be able to do this if we could somehow make the Motoko compiler continuable across rounds. Not sure about rust…does rust compile rust? For dexs, should @sonic_ooo , @ICPSwap , @HelixMarkets , and @ICLighthouse they be checking total supply on each transaction and not letting the transaction through if they detect a massive change in total supply? More to dig into here when I have more time. In the meantime I hope I’ve minimized the damage and we can get YC back online. Along those lines I did set up utiy3-bqaaa-aaaam-abe7a-cai.… which is a VOIC canister(github.com/icdevsorg/VoIC) pointed at the newish YC canister. It is in the process of syncing, but when done, it should track ongoing activity and update votes accordingly. People can make proposals and everyone can vote without burning. It even has some treasury functions should we decide to use them. I’d suggest we move all YC decisions over there until we get this DAO transition stuff figured out. If it looks like your balance is out of whack, let me know and I’ll investigate.
7
8
34
3,025
It takes less than a minute to mint $ICDV and fund public goods on the Internet Computer at icdevs.org/donations.html.
3
9
38
3,090
1/ I'm sitting at the " #AccountAbstraction " off-site at #ethDenver. I'm going to have to find someone to explain how canister wallets + tecdsa on the #IC doesn't make most of these presentations irrelevant.
2
9
30
3,263
It has been a couple of wild weeks trying to bring together something new with a host of folks across the #IC ecosystem. At ORIGYN we have a couple of internal tools that are essential to the operation of the ORIGYN network, but that are not directly aligned with our mission. Because the ecosystem is so young we are having to incubate these essential tools inside ORIGYN and we've been considering ways to spin them out. Some have obvious tokenomics applications and some do not. When Byron at @can_scale approached us about acquiring the CanDB IP, it aligned with a number of internal initiatives. We also recognize that CanDB needs more funding before it reaches its full potential. Byron approached us with the idea of a license that projects can grow into and that kicks expenses down the road to a period when the projects will be more able to handle the expense of a software license. The license can be paid with cash for traditional businesses, but we are really excited about giving projects that use our software the opportunity to pay with tokens generated in their decentralization sales. By doing this we create an interdependence that transcends the typical supplier/customer dynamic. The drive of the developing organization is no longer focused on maximizing the profitability of the software, but on making our customers as valuable as possible. Ultimately these software and license rights need to be handed to an organization focused on supporting and extending the software, organizing maintainers, funding development, and enforcing the open source and license responsibilities of software users. For now, the Origyn Foundation(@ORIGYNTech ) will play the role and any software user may gain governance rights through the OGY token. In the future, we hope to move these rights to an organization more suited to the task, more decentralized among the software participants, and with an evolution of this license that relies more on intrinsic incentives than legalese and enforcement. We do not think that this is the final version of this license, but we are excited about the 1.0 version we were able to get to under the time constraints. We are looking forward to maturing it and have been bouncing ideas like tokenization, pay by stake, and other creative ways to make CanDB and other software we are developing into a public good with a built-in funding mechanism. If you'd like to help steer that vision you can at github.com/ORIGYN-SA/OFSL. I also want to recognize the work and sacrifice that Byron put into CanDB to get it to this point. Our licensees would not be considering this type of arrangement if Byron hadn't bootstrapped CanDB out of nothing. Our current funding mechanisms rarely reward appropriately and we have done what we can to keep Byron aligned with the project and having a healthy upside. But we need to do better for our entrepreneurs and those trying to build would-be public infrastructure for the Internet Computer. We hope that this license moves us toward a better second-stage solution, but we will also keep searching for a solution to the bootstrap stage as well. I'll be talking more about this on a space later today: nitter.app/i/spaces/1ynJOaO… (Sorry for the super post....I tried to thread the thing out and Twitter ate it...I ran out of time.) #Funding #SNS #GreenPill #RegenFinance #opensource
3
4
31
1,988
Hey #ChainFusionSummer, what are doing to make the IC the nexus point for i, ii, and iii?
Replying to @jon_charb
Synchronous atomic composability is very overrated imo. Like, think about what are some specific cross-L2 things *you* are already doing or envision yourself doing that could be more seamless. For me, the top two are: 1. I have coins on Optimism, I want to pay Bob, but Bob is only on Arbitrum. 2. I have coins on Taiko, I want to use a dapp on Polygon, so I need to send-to-self to Polygon in order to use that dapp. These are not fancy nerd problems that can be fixed by solving synchrony. These are UX problems that can be fixed with: (i) widely adopting ERC-3770 so that the chain is part of the address, so an address once again becomes a self-contained "how do you pay me" identifier (ii) a cross-L2 exchange protocol (eg. ERC-7683), so you can do cross-chain sends programmatically without juggling which specific intermediaries to trust and which APIs to connect to (iii) wallet integration, so sending cross-L2 is done by putting the recipient's ERC-3770 address into the exact same textbox as you use for regular sends today Solving nerd problems *can* make this much more efficient, especially by making cross-chain swap markets more friendly to liquidity providers, by reducing withdraw times from 1 week (optimistic rollups) to 1 hour (zk rollups today) to 1 slot (ideal zk rollups with proof aggregation). But even there, there's multiple orders of magnitude of unclaimed gains that don't even require getting into synchony.
2
8
35
2,607
Appropriately I've been too busy to keep up with this, but if you are a builder in the space and want to get on this list, let me know. The dao hasn't elected any new proposers than me because that are all too busy building. . pnbcw-3qaaa-aaaag-qbpqq-cai.… Maybe we need an @OpenChat channel.
4
5
33
2,564
My no-so-brief write-up from the @psychedelicDAO town hall this morning. TLDR: Good, Bad, Solution, Let's discuss, I have a lot to learn. forum.dfinity.org/t/psychede…
1
8
36
8/ This lets smart contracts on the #IC control, publish, and interact with any #evm chain without a bridge. You only have one contract to secure instead of two (thus a pier instead of a bridge).
1
5
33
My new video is out. All about ICRC-1 and a code deep dive into how it works.
ICRC Fungible Part 3! What is ICRC-1? We were not quite able to get to building the minting dapp for ICDV this week, but we have a video anyway. Today is a deep dive into the ICRC-1 standard and looks at the code that runs an ICRC-1 token. Video in reply 👇
1
7
34
2,540
1/2 I'll be presenting some tech I built with a #Dfinity grant at 11AM Central today on the Dev Discord discord.gg/cSt9qX2v. We've built some tech that lets you host NFTs/Media on-chain and manipulate it upon request according to the context of the requestor.
1
6
32
2/ In mumbai.polygonscan.com/tx/0x… I sent an NFT from @austingriffith's and @webopsx's ETHScaffold demo deployed to mumbai to a @dfinity #IC smart contract(canister).
1
4
29
10/ @ORIGYNTech will be using this tech to bring your non-IC NFTs to the #IC and to bring your #IC NFTs to trusted marketplaces on evm chains with protected creator royalties. Reach out if you want to know more.
2
7
30
Forced selfie.😀 #icpcc2023
2
33
1,140
1/ Potentially unpopular #IC #SNS lightly held opinion(you are welcome to change my mind): If you can’t build your own DAO layer then you shouldn’t be trying to run one.
3
6
34
Let it be known that @daviddalbusco is a gentleman, a scholar, and a damn fine hacker. Thanks for the help!
2
1
32
1,090
I went 0/3 on SNS-1 Airdrop. How about you?
22
33
Azle is getting crazy awesome features. Awesome work @lastmjs!
Azle 0.21.1 now has support for large asset uploads of up to 2 GiB in size, stored in the Wasi filesystem on the heap Just specify src/dest in your dfx.json file to get these assets uploaded during deploy Stable memory filesystem with even greater size limits is coming soon :)
1
4
34
1,291
I don't think "not your keys, not your crypto" is sufficient for the #IC. It is becoming "not your code, not your crypto". You don't just need to own the canister, you need to trust the code and that requires open source.🧵
4
10
33
3,806
I just backed a project on @crowdfundnft. Help get it fully funded! kn5ky-6iaaa-aaaai-qbikq-cai.… Fly away Seers! cc @SeerMarkets
1
28
7/ What does this mean? Everything in crypto shifts. Need a non-custodial wallet? It is the #InternetCoputer. No one has that key. It exists in alien math and can only sign via t-ecdsa.
2
5
29
I guess I can prop up my soapbox a bit. I'll caveat this with the fact that I'm not a DeFi expert, so there are likely some corners of it that I'm completely ignorant about. I've spent the last number of years working toward systems that I'll call xFi for lack of a better term. In this case "x" means: Down with excess rent extracting capitalism while also saying Isn't capitalism AMAZING! The core of it is that undue economic rent is a powerful engine and makes capitalism go...it has given us the massive productivity and wealth gains of the last couple of centuries. But it also absolutely preys on the weak and ill-informed. xFi attempts to balance the opportunity of taking risks for large gains with establishing responsibility and accountability for those who want to participate at the edge. It reduces the ability for people with an unfair advantage to shift existential risk onto the rest of us...or at least attempts to provide all of us with some of the benefits of this upside. WTF does this have to do with EVMs, DeFi and the IC? Well, I think EVM Defi has a bit of cancer at its core. It conceals information with its linear execution. Those with imbalanced info and access prey on those without the info(MEV). The one thing that an actor model gives you is the ability to level the playing field a bit. Your smart contract can actually sandbag itself, distribute information and assure that everyone is getting the 'best deal'...further it can charge for that privilege and, as a DAO distribute that value to the broader ecosystem. It boils down to a decision of speed vs. fairness. Now those that have speed and information want to keep their advantage...and retail has no idea how much they are actually being raked over the coals. This isn't new...see the story about wanting to own a bank on a corner lot so you can put deposit rates on one side and interest rates on the other. Can we convince or show 'retail' that they are being raked over the coals and/or that they are way overpaying for convenience/speed? Hard problem. I'm not sure. Right now everyone is just trying to copy what works on other chains onto the IC. I guess, yeah, 'classic' defi isn't going to fly because of the lack of linear execution(unless you get everything on a swapper(h/t @anvil_ic ) canister where single-threaded execution can give the same effects as an evm(or just do an evm like @bitfinitynet is doing). But that isn't the endgame. The endgame is one where you can buy(or be awarded) the token that the value goes to....and those that accumulate can't just sit on the value...but that it keeps turning over in a way that makes everyone wealthier while maintaining the turbo engine of capitalism. I think the IC is the best place to build THAT system right now. We need to build a lot of infrastructure to get there. Sorry for the long thread. #HappyNewYear #xFi
I am not going to make a definitive statement since I am not an expert and the SMEs believe it can be done (@afat). But what I can say for sure is the current DeFi UX isn't great. I have tested Bitfinity test. The UX is awesome.
3
10
30
3,818
12/ I should mention that the nft asset itself is also hosted on the #IC blockchain at exos.origyn.network/-/ethmex… complete with an experience page at exos.origyn.network/-/ethmex… and a host of dapps like a ledger explorer, wallet, marketplace, library viewer (multiple assets support).
2
26
11/ Thanks to #EthMexico for the opportunity to focus on this for a solid period of time(sorry we didn't finish during the weekend) and to my team at Origyn, specifically FerMartz and Rafael who stayed up hacking with me...and @reqwium for the art.
1
2
28
I’ve made two proposals to try to reduce spam on the NNS of the #InternerComputer forum.dfinity.org/t/proposal… and forum.dfinity.org/t/proposal…
1
7
27
Hey. Can we not create a massive clusterf*** by calling something other than the NNS based asset deployed by dfinity ckAnything? It is just going to confuse the hell out of users when they try to send it to the NNS and it gets "lost". Then we lose an IC user.
2
2
29
1,358
If you guys want to be able to add non-SNS tokens to the NNS, you should mash the up button here: dx.internetcomputer.org/topi…
3
10
28
2,743
Just spitballing here..but if Bitcoin isn't a security, and we can put the whole state in a canister, and we fork it, then overlay governed rules, new distribution patterns(like a big fat fresh mint)...is it a security? We also inherit a ton of holders. Sorry...trying to get a vacation in and I've obviously failed at getting out of work mode...but have gotten far enough away to let some ideas go off the rails.
1
3
25
2,184