s4.sol

// s4 : Swarm

contract swarm {
    
    struct Member { bool exists; }
    struct Claim {
        uint unproven;
        address[] refutors;

jtremback

I am not actively updating this gist and it is already out of date. Please see http://altheamesh.com/documents/universal-payment-channels.pdf

Universal Payment Channels

Jehan Tremback

Zackary Hess

Introduction

datagotchi

// @title: Datagotchi
// @author: Doug A <d11e9@turkd.net>
// @desc: distributed data modeling

contract datagotchi {
    
    struct HashedResponse {
        address creator;
        bytes32 hashedReponse;

content

import "github.com/d11e9/avatar/contracts/avatar.sol";

contract Archive is owned {
    
    struct Content {
        bool exists;
        address OP;
        bytes32[] archives;

RevokableOwned

import "owned";

contract RevokableOwned is owned {
    address previousOwner;
    uint8 revokableV;
    bytes32 revokableR;
    bytes32 revokableS;
    
    // In order to make a contracts ownership revokeable you must

content

import "owned";

contract Archive is owned {
    
    struct Content {
        bool exists;
        address OP;
        bytes32[] archives;
    }

zelig

Swarm is a distributed storage platform and content distribution service, a native base layer service of the ethereum web 3 stack. The primary objective of Swarm is to provide a sufficiently decentralized and redundant store of Ethereum's public record, in particular to store and distribute Đapp code and data as well as block chain data. From an economic point of view, it allows participants to efficiently pool their storage and bandwidth resources in order to provide the aforementioned services to all participants.

From the end user's perspective, Swarm is not that different from WWW, except that uploads are not to a specific server. The objective is to peer-to-peer storage and serving solution that is DDOS-resistant, zero-downtime, fault-tolerant and censorship-resistant as well as self-sustaining due to a built-in incentive system which uses peer to peer accounting and allows trading resources for payment. Swarm is designed to deeply integrate with the devp2p multiprotocol network layer of Ethereum as wel

holiman

Stopping spam

This blog post by Jonathan Brown suggested replacing SMTP with Ethereum blockchain; specifically, utilizing the log channel to monitor events.

With this approach, emails wouldn't actually be stored within the EVM (Ethereum Virtual Machine) storage, but every email would still be present in the blockchain blocks. The EVM log mechanism would make it simple for a full node to monitor and be alerted whenever an email was submitted.

I don't believe that this would be feasible in the real world, for several reasons

• There are lots of email being sent, some of them quite large
• Most people wouldn't want their emails forever on the blockchain, the future resiliency of GPG is unknown, and GPG encryption does not provide perfect forward secrecy. Once a key is compromised, all is revealed.

jorisbontje

#!/usr/bin/env python
#
# @file   echo.py
# @author Wei-Ning Huang (AZ) <aitjcize@gmail.com>
# 
# Copyright (C) 2013 - 2014 Wei-Ning Huang (AZ) <aitjcize@gmail.com>
# All Rights reserved.
# 
# This program is free software; you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by