Skip to content

Instantly share code, notes, and snippets.

View pipermerriam's full-sized avatar

Piper Merriam pipermerriam

  • Ethereum Foundation
  • Boulder Colorado
View GitHub Profile
@pipermerriam
pipermerriam / ecverify.sol
Created October 17, 2016 16:35 — forked from axic/ecverify.sol
Ethereum ECVerify
//
// The new assembly support in Solidity makes writing helpers easy.
// Many have complained how complex it is to use `ecrecover`, especially in conjunction
// with the `eth_sign` RPC call. Here is a helper, which makes that a matter of a single call.
//
// Sample input parameters:
// (with v=0)
// "0x47173285a8d7341e5e972fc677286384f802f8ef42a5ec5f03bbfa254cb01fad",
// "0xaca7da997ad177f040240cdccf6905b71ab16b74434388c3a72f34fd25d6439346b2bac274ff29b48b3ea6e2d04c1336eaceafda3c53ab483fc3ff12fac3ebf200",
// "0x0e5cb767cce09a7f3ca594df118aa519be5e2b5a"

.eth Registrar using only Deposits.md

This is an attempt of setting up a name registrar that use deposits instead of burning or token contributions and tries to optimize name utility and reduce domain squatting. Previous initiatives of charging a "rent" based on the market price with an yearly auction proved impopular with many developers as they believed the registrar wasn't delivering any value for the "tax" as well as worries that a sudden big auction could force someone unexpectedly to be forced to sell the name.

In order to start doing that let's define the problem:

Name squatting is defined as buying a name and not adding any value to it, just holding it expecting that domains names will become more valuable in the future. Let's assume that all name buyers have the intention of acquiring a name and make it more valuable over time, either by working on it as a business and adding value to the "brand", or by working to increase the chances of finding a

{
   "Statement":[
      {
         "Effect":"Allow",
       
         "Action":[
            "s3:ListAllMyBuckets"
         ],
         "Resource":"arn:aws:s3:::*"
      },
#greenfield customersUPDATE accounts_account
SET treatment_group_info_id = 2,
treatment_start_at = '2013-07-01'
WHERE base_account_ptr_id IN
(
SELECT id
FROM accounts_baseaccount
WHERE unique_id IN (0009147791,0022010493,0033361590,0035653573,0037780635,0044655192,0047876755,0049146796,0049571940,0071065195,0071434645,0074803866,0077358037,0662234728,0677563370,0707681758,0744021690,0767348621,0817655299,0887581777,0890104444,1000418950,1013700556,1049316306,1092207087,1161816870,1167014058,1239396850,1257974530,1272317504,1282730199,1284981550,1293983839,1312529759,1372450962,1372462720,1404999703,1437913580,1481373336,1504839900,1525395878,1547115623,1624937409,1669153405,1675646537,1711363326,1726435508,1830917506,1831184323,1876165393,1944378724,1966608865,1968382453,2003670060,2050577405,2075500188,2136251620,
2199590355,
2216208876,
@pipermerriam
pipermerriam / mixins.py
Created November 7, 2012 16:07 — forked from vdboor/mixins.py
Django view initialization ordering issues
class BaseViewMixin(object):
def dispatch(self, request, *args, **kwargs):
# Set earlier to ensure that other class methods which expect
# these values to be present can be called in `init`
self.request = request
self.args = args
self.kwargs = kwargs
# Run the complete request, returning a response, but allowing
# `init` to either raise exceptions, or hijack the response if