• Breaking News

    Thursday, June 7, 2018

    Home Unlabelled Ethereum Andy Warhol Art To Be Sold For Bitcoin Via Ethereum Blockchain

    Ethereum Andy Warhol Art To Be Sold For Bitcoin Via Ethereum Blockchain

    June 07, 2018

    Ethereum Andy Warhol Art To Be Sold For Bitcoin Via Ethereum Blockchain

    Andy Warhol Art To Be Sold For Bitcoin Via Ethereum Blockchain

    Posted: 07 Jun 2018 09:40 AM PDT

    Brave reaches 2.7M monthly active users

    Posted: 07 Jun 2018 04:16 AM PDT

    The 0x Mission and Values – 0x Protocol

    Posted: 07 Jun 2018 05:13 PM PDT

    Enigma Project at Consensus

    Posted: 07 Jun 2018 04:35 PM PDT

    Week in Ethereum News: June 7, 2018

    Posted: 07 Jun 2018 10:53 AM PDT

    Vitalik Cautiously Supportive Of Blockchains Use For Online Voting

    Posted: 06 Jun 2018 10:59 PM PDT

    New Ethereum project "stamps" ERC20 to make them behave like ERC721's

    Posted: 07 Jun 2018 11:06 AM PDT

    FanChain/Sportscastr just announced a Ethereum-Based sports media platform with a token model that I haven't yet seen before in the Ethereum ecosystem

    From the Whitepaper:

    FanChain tokens are based on the ERC20 standard but also adopts ERC721-style features when they are distributed or accepted within the FanChain ecosystem.

    Similar to the concept of a "colored coin," FanChain tokens are the synthesis of a fungible token with a non-fungible token. Although the FanChain token is fully ERC20-compliant, its implementation of the ERC20 specification allows for additional information to be stored on a per-address basis. This additional metadata contains the breakdown of an addresses' token balance by team, league or event.

    FanChain tokens can be transferred and monitored by any ERC20 compatible wallet without care or concern of the extra metadata ("stamps"), but the extra data associated with each stamped token (e.g. team or league breakdown) becomes visible in FanChain-aware systems.

    How the Tokens are "stamped"

    Has anyone seen this model before? I think it could be a cool new feature that enables a new niche of projects on Ethereum. Especially with loot-based games that use Ethereum's tokens, because these types of games will be very heavily dependent on ERC721 type features.

    Also, if you haven't checked out FanChain on your own, you should definitely do so. I hope the best for this project; it could potentially bring on a ton of new people into crypto through the integration of a Streaming/Twitch-like platform for sports commentary and being able to incentive fan produced content, in a similar way to Basic Attention Token and how it incentives Publishers to get paid from their fans rather than from advertisers.

    plus they have David freakin Stern working with them. Talk about consumer adoption potential

    https://fanchain.com/

    submitted by /u/davidahoffman
    [link] [comments]

    Lets talk about the Constantinople (Phase II) Metropolis HF. Is it possible we could see EIP960 and EIP1011 implemented?

    Posted: 07 Jun 2018 05:07 AM PDT

    120M ETH Supply Cap: https://github.com/ethereum/EIPs/issues/960

    Casper FFG: https://github.com/ethereum/EIPs/blob/master/EIPS/eip-1011.md

    Curious to hear from any Ethereum Core developers, informed community members/developers on these EIPS as it seems both of these have had quite a lot of discussion about both being beneficial to enhancing network security.

    submitted by /u/OperationNine
    [link] [comments]

    FOAM and the Dream to Map the World on Ethereum

    Posted: 07 Jun 2018 06:40 AM PDT

    With stateless clients can we eliminate the transaction receipts from sharding?

    Posted: 07 Jun 2018 03:20 PM PDT

    I just read over the Sharding Developer Doc and got to the part about Stateless clients.

    Here, our goal is to avoid requiring validators to store the state of the entire system (as that would be an O(c2) computational resource requirement). Instead, we allow validators to create collations knowing only the state root, pushing the responsibility onto transaction senders to provide "witness data" (i.e., Merkle branches), to prove the pre-state of the accounts that the transaction affects, and to provide enough information to calculate the post-state root after executing the transaction.

    I'm blown away. But it occurs to me that if we can do stateless clients, then we should be able to eliminate the whole receipts mechanism, and implement super simple transaction-only sharding; that is use dynamic shards of the state, such that there's never any need for cross shard communication.

    With the current sharding implementation it seems to me that almost all transactions will cross shard boundaries, and therefore require the transaction receipts. I realize that this still represents a huge capacity increase, since each receipt only affects two shards out of 100... but wouldn't it be easier to avoid those receipts...

    To my thinking, since most transactions are simple, and only affect two Ethereum addresses, we should be able to define dynamic shards that are almost always independent. The basic idea is inspired, loosely from EIP #648, Easy parallelizability, in that the shards could be defined by examining which address(es) are modified by each transaction. I thought that this approach (dynamic shards) was abandoned because it required that every shard node have access to the entire state data:

    These efforts are admirable and may lead to some gains in efficiency, but they run into the fundamental problem that they only solve one of the two bottlenecks. We want to be able to process 10,000+ transactions per second without either forcing every node to be a supercomputer or forcing every node to store a terabyte of state data
    VB. moderately-simple-but-only-partial-ways-of-solving-the-scalability-problem

    But if nodes are supplied with the relevent state along with each transaction, then all that remains is dividing up the transactions... Dynamic shards could be assigned by simply going through all pending transactions, conceptually: 

    for (tx: all pending transactions) shard=primary_dest(tx); if (assign_all_addrs(shard) { assign_tx_to_shard(tx, shard) } else { save_tx_for_next_block(tx); } }

    once a transaction's addresses have been assigned to a shard, then none of those addresses can be assigned to any other shard (for example, if they are referenced in a different transaction). If an address appears in two transactions, and those two transactions would have been assigned to different shards, then we say that the two transactions have a collision. And in that case one of the transactions would be deferred to a later block.

    To reduce collisions it would be advantageous to make the assignment of tx's to shards based on a hash of the primary destination address (with the source address and secondary destination addresses assigned to the same shard). The reason to use the primary destination address instead of the source address is that it will reduce collisions. That is, it's very likely that there will be multiple transactions in the tx-pool with the same destination address (crypto-kitties, bitPay, or some other contract); however it's much less likely that there will be many transactions with the same source address.

    So what I'm asking is, if I'm understanding the potential for stateless clients correctly, then why do we need transaction receipts at all?

    PS. Thanks in advance to those of you who take the time to help me sort this out!

    submitted by /u/mysticmonsoon
    [link] [comments]

    Where is a good place to apply for ethereum jobs?

    Posted: 07 Jun 2018 02:27 PM PDT

    I'm trying to get an ethereum job in the space, what are some good websites for ethereum jobs?

    submitted by /u/alazysurfer
    [link] [comments]

    Creating An Easy Onboarding User Experience For The Raiden Network.

    Posted: 07 Jun 2018 06:41 AM PDT

    How Polkadot tackles the biggest problems facing blockchain innovators

    Posted: 07 Jun 2018 08:47 AM PDT

    Driving Solidity gas fees into the green

    Posted: 07 Jun 2018 09:16 AM PDT

    Human Readable Contract ABIs using Solidity signatures - ethers.js

    Posted: 07 Jun 2018 09:53 AM PDT

    Call for partnership at the ENS Workshop & Hackathon 2018

    Posted: 07 Jun 2018 06:46 AM PDT

    Interesting interview with EOS block producer candidate .GENEREOS from Australia - June 8 on Crypto Finder

    Posted: 07 Jun 2018 06:58 PM PDT

    Quebec Hydroelectric cuts power to mining companies temporarily

    Posted: 07 Jun 2018 05:48 PM PDT

    FourthState Team from 'Blockchain at Berkeley' secures ETF Grant and will have Plasma Chain working by the end of August

    Posted: 07 Jun 2018 06:49 AM PDT

    What happened to Easy parallelizability · Issue #648 · ethereum/EIPs?

    Posted: 07 Jun 2018 05:14 PM PDT

    Let's research projects for the benefit of the whole community. Qfellow Season is HERE!

    Posted: 07 Jun 2018 06:06 AM PDT

    https://i.redd.it/a4htiaklbi211.jpg

    TL;DR: I want to apply right now => Qfellow Application

    The Qfellowship Program is the backbone of ConcourseQ, the original ICO due diligence community. The ConcourseQ community has completed full due diligence reports on hundreds of ICOs in the first 10 months of its existence and our work has included:

    • Issuing warnings on 171 different ICOs.
    • Publishing 14 editions of Terrible Token Tuesdays.
    • Being directly responsible for shutting down two fraudulent ICOs (Moirai and Cvent).

    We maintain this database so that anyone can get a second opinion from a seasoned community member before taking the plunge.

    You may have heard of other projects raising millions of dollars to research ICOs and wonder how ConcourseQ is any different. To start:

    • No exploitative volunteer labor: We value our Qfellows and compensate them accordingly with $350/month worth of ether to share their research with the community. ConcourseQ has never collected revenue and we are not planning to in the future.
    • Springboard to full time employment: Three Qfellows have transitioned from an old economy job to working full time in the space, while one of our student Qfellows secured a summer internship as a token analyst. All work on ConcourseQ is publicly verifiable and we enthusiastically support Qfellows that want to transition to building.
    • Part of a broader open organization: The Qfellowship program is a cornerstone of the Concourse community. Many Qfellows have also worked on other community projects such as the Layer2 token curated feed.
    • Not doing an ICO: We need the independence to call out scams. Exorbitantly funded ICO research startups are conflicted between courting ICOs to join their TCRs and calling out fraud. We are here to speak truth to scammers.

    If you like what we are doing, but do not have the time to be a Qfellow, please consider helping us by amplifying or sharing this message. The more people that hear about Qfellowships, the more people will apply, the more new Qfellows we can onboard and ultimately the more free research we can do for the community.

    Where does the money for Qfellows come from?

    Our pockets. If anyone reading this is interested in supporting this work by sponsoring additional Qfellows, please get in touch. We fund the Qfellowships that we can afford, but with more help, we could expand the program faster. ConcourseQ is technically for-profit at the moment, but we are researching how to convert ConcourseQ to a non-profit entity with an open-source code base.

    Apply here: (4 minutes)

    Qfellow Application — https://docs.google.com/forms/d/e/1FAIpQLSczKfV_iBxPITTIeebFSSWAGC0aTBnXl6pjuf63HB6xHO1O1g/viewform

    submitted by /u/scott_lew_is
    [link] [comments]

    Making Sense of Web 3

    Posted: 07 Jun 2018 08:30 AM PDT

    Bancor’s Recent Token Promotion Gets Thumbs Down From Crypto Community

    Posted: 07 Jun 2018 08:41 AM PDT

    25+ ERC-20 Tokens now natively supported on all KeepKey hardware wallets!

    Posted: 07 Jun 2018 03:10 PM PDT
    Read more
    at

    No comments:

    Post a Comment