Digix provides a transparent, auditable, and secure protocol that leverages the full potential of Ethereum's peer-to-peer decentralized consensus system and IPFS permanent document storage to facilitate the creation of transferable crypto assets on the blockchain.
A vital tool for us in the future will be Decentralised Web Technologies such as Ethereum and IPFS. Ethereum is a Decentralised Virtual Machine that anyone can deploy censorship-resistant applications to. Aragon is an early example of a censorship-resistant application built on Ethereum.
Greetings from the shortest person of the MetaMask team! I have an announcement: MetaMask has gotten together with IPFS and Ethereum-JS to bring you... (drum roll) The "IPFS Ethereum DApp Hackathon" or as i would like to call it: The IPFS Ethereum Dappathon. It will take place in Seattle but it is a remote/hack at home-athon. Submissions will be accepted online and more details on that soon to come. for further information checkout the meetup page: https://www.meetup.com/Seattle-IPFS-Meetup/events/236101964/ The winning entry will get an interview with everyone's favorite Ethereum podcast host, Sir Arthur Falls! Be there or be square, and help nudge the Dapp-o-system forward!
BigChainDB, IPFS, Ethereum -- which one(s) are appropriate for my application?
I'm working on project and I'd like to incorporate one or more blockchains in it -- simplicity is the priority, but I also want to use the appropriate tools for the task. Without going into much detail, I'll just say that my needs are as follows:
permanently store public data in a distributed manner
allow users to audit the entire history of their own private transactions
allow users to authorize other users to make transactions for them -- also allow the former user to revoke authorization
Here is my present understanding of how these three technologies should be used and how they might apply to my project:
IPFS seems like the base technology that's required -- a decentralized file system that can permanently store information.
BigChainDB seems like it may not be absolutely necessary, but will greatly simplify development as it provides the ability to permission data stored in IPFS and enables querying and such.
Ethereum seems like it's pretty unnecessary, but I thought it might be useful for enabling users to contractually authorize other users to make transactions for them...on the other hand, it seems super simple to codify this in the application logic.
So, I guess what I'm hoping to learn is:
Is BigChainDB useless without a data store like IPFS, or can I just use BigChainDB as a standalone database to keep all my application data inside of?
If BigChainDB can be used by itself as a data store, then what benefit does IPFS provide? How do these two technologies interact in the context of a given application?
Am I correct in assuming, for some use case as simple as mine, Ethereum is overkill?
-- Edit for clarification -- The way I imagine I should use these technologies is as follows: (a)
store application data as content addressed information in IPFS
use content addresses as field values in Mongo collections effectively mapping appropriate data to users
store the application data in BigChainDB directly (adding it to the appropriate Mongo collections)
-- Edit 2 -- After reading some more, it now seems to me that BigChainDB can (and in my case should) be used on its own. I'm seeking global consensus on data and I need to query it, so I don't think IPFS has a purpose in my application. I'm supposing that Ethereum would only be useful to me if I intend to have the server run in a distributed fashion as well, correct? I would like that, but I feel that time constraints will limit my deployment options to what I'm already familiar and comfortable with...
Hey all! We're hosting a remote IPFS & Ethereum Coding Workshop on September 5th & 6th. We'll be covering Smart Contract Fundamentals, Ethereum Concepts, building Core Components of both systems, and, most importantly, how to build a project combining these two systems. Most of the workshop will take place in a collaborative live coding environment. If you have any questions, ask away or you can learn more here!
Ethereum IPFS Hackathon *reminder* and Open registration announcement
Hello again, As a friendly reminder, the MetaMask team, along with IPFS and the eWASM team, is hosting an Ethereum IPFS DAppathon. Registration starts...NOW! You can register here https://github.com/MetaMask/IPFS-Ethereum-Hackathon by opening an issue. Please read the README it has useful info. It's also a living document so info will be updated periodically. So keep an eye out for changes. DApp submissions will close on Friday, February 10th by 9:00pm GMT At that time registration will close and all registration issues will be locked. More information can be found both on the GitHub repo's README and here: meetup.com/Seattle-IPFS-Meetup/events/236101964/ (http://meetup.com/Seattle-IPFS-Meetup/events/236101964/) In-person events will be streamed for those who can not attend.
The aim of ATMarketplace is to support all the fantastic decentralized applications that are growing in size and numbers. Currently the project supports IPFS, Ethereum, Bitcoin, ZeroNet, CJDNS, I2P, BitMessage, Scuttlebutt and many others. The apps with simple installers can be downloaded and installed within the ATMarketplace app itself. There more complicated apps can be installed externally and then linked to within the app. Even though the project is still early alpha, I am trying to spread the word and determine if its worthwhile to continue development or not. You can find more info at http://atmarketplace.eth.show there you will find demo videos, contact methods and of course the app to download and play around with. I've just created a chat room at #atmarketplace:matrix.org and haven't put it on the main website yet. Drop in and say hi.
IPFS-REDUX STATE : A recording of my Fullstack hackathon presentation.
https://www.youtube.com/watch?v=XOCeA5luqrs&index=12&list=PLx0iOsdUOUmmAlZLrrWste69LFdusC37D&t=8s So I presented this hackathon trying to build upon the IPFS based "linked list" idea for extracting local state to the global state pool. The project ended up being too large to complete fully during the Fullstack Hackathon, but I think the idea is very interesting and I really wanted to share. In this implementation, I'm using IPFS, Ethereum and OrbitDB to allow people to create their own "stores" online that then can exist without 'me' the server provider. (The store code exists in IPFS, so does the store state). It's not fully realized, but I'll working at it. First steps will actually be to simply significantly the system as I'm using React-Redux and kinda let the app blow out of proportion. That said, cool thing- IPFS is in browser as is OrbitDB (OrbitDB is instantiated but I don't get around to storing data in it. It was about 48 working hours as a single person, so you know, Only was able to do so much. Here is the code as well, it will probably be of minimal help to anyone and I made a lot of tradeoffs so it's not best practice by any means, but some might find it interesting. Feel free to shoot me any questions as well! https://github.com/crazyrabbitLTC/IPFS-Redux
Eternum is a simple and easy-to-use IPFS pinning service. It will host your IPFS files so you can be sure they'll always be available, and it comes with an API that you can use in your applications. And it only costs $0.14/GB per month. Ethereum Name Service (ENS) and Protocol Labs (the original creators and stewards of IPFS) are proud to present the next step in ENS + IPFS integration: EthDNS. This builds on earlier work ... IPFS + Ethereum Storage. We will create a simple datastore solution using IPFS and Ethereum. IPFS provides a convenient interface for distributed data storage, with a hash-based content address for reference to our file. This address will be stored in our smart contract on a private Ethereum blockchain. Ethereum & IPFS APIs. Develop now on Web 3.0. Our development suite provides instant, scalable API access to the Ethereum and IPFS networks. Get Started for Free A simple DApp to upload a document to IPFS and then store the IPFS hash on the Ethereum blockchain. Once the IPFS hash number is sent to the Ethereum blockchain, the user will receive a transaction receipt. We will use Create-React-App framework to make a front-end. This Dapp works with any user that has MetaMask installed in their browser.
1) a short introduction to IPFS for those new to it. 2) an update on important Ethereum-relevant developments since DEVCON1. 3) js-ipfs, the IPFS implementation on the browser, for Web3 Apps. 🛠️ Connecting ETH to IPFS How can you connect Ethereum and IPFS? Austin Griffith (Ethereum Foundation) will be going through a quick getting started guide and example dapp for HackFS. MetaMask hosted events. Right now, we're gearing up for the Ethereum-IPFS Hackathon in Seattle: meetup.com/Seattle-IPFS-Meetup/events/236101964/ 🤑 Learn how to become a highly paid blockchain dev: http://www.dappuniversity.com/bootcamp 🔴 Subscribe to this channel: https://www.youtube.com/channel/UCY0x...