Search content
Sort by

Showing 19 of 19 results by koeppelmann
Post
Topic
Board Announcements (Altcoins)
Re: Gnosis - the decentralized prediction market platform and oracle standard
by
koeppelmann
on 21/05/2019, 00:48:12 UTC
Hey everyone.
Coming here to make sure you are aware of 2 dates:

1) Currently you can lock your GNO to generate OWL. The lock period is only open the next ~30h. After the lock period you can immediately claim your GNO back. Every GNO generates you 2 OWL = $2 fee credits for everything Gnosis builds.

Currently you can use OWL in the dutchX and with the Gnosis Safe (to pay for gas).

2) The dxDAO will start very soon. (May 29th)
It is a radical DAO experiment to test on chain governance. We will hand over control of the dutchX to this DAO. We think that governance is a critical piece of decentralized systems and we want to gain experience as early as possible.

All relevant information around dxDAO here .
Post
Topic
Board Announcements (Altcoins)
Re: Gnosis - the decentralized prediction market platform and oracle standard
by
koeppelmann
on 05/01/2018, 09:36:38 UTC
Hey everyone, check out the latest update of our website: gnosis.pm
Post
Topic
Board Announcements (Altcoins)
Re: Gnosis - the decentralized prediction market platform and oracle standard
by
koeppelmann
on 21/12/2017, 22:19:34 UTC
any reason why it keeps falling while almost every other coin, with 100mil+ supply has doubled?
Because GNO is shit without community and any feedback from devs. They don’t work, we don’t receive any product, only photos with meetups and articles lol.

Actually, this is not really so, they do have AMA and publish announcements in official slack, and they publish news in the blog, what is true they are not active on this forum, but this was from the start they didn't pay much attention to this forum.

Hey, Martin from Gnosis here.
Sorry, indeed we forget a bit about bitcointalk and this thread.
However - we do monthly community calls with AMA and details updates on our product work. Check out: https://www.youtube.com/channel/UC3bfClXlBRHv6BXx1TcBeGg
We have a bunch of projects in the pipeline. Beside the core prediction market platform and applications on top, a decentralized auction based exchange (that will later also be used by prediction markets) and a consumer friendly multisig wallet.

Just have a look at our Github and you will realize that we are working on many things in parallel: https://github.com/gnosis/
Our team has grown to over 30 now.

Currently most important: we released the first application on Gnosis: "Olympia". To give everyone a chance to try it for free and get familiar with the concept we have first deployed it on Rinkeby (a testnet) and started a tournament.

olympia.gnosis.pm

Rules are simple:
 1. You need Uport (click on "Connect a wallet")
 2. You will get 200 OLY tokens every other day
 3. Use those tokens to make predictions
 4. If on Jan 5th you are among the top 100 users you win GNO)

Let us know what you think.
Post
Topic
Board Deutsch (German)
Re: CoinTracking - Gewinn/Verlust Portfolio und Steuer Reporting für digitale Coins
by
koeppelmann
on 19/11/2017, 12:35:03 UTC
2 kurze Fragen:

1) Habe das Programm eben zum ersten mal ausprobiert und noch keine PRO/UNLIMTED version gekauft. Ich kann dennoch einen TAX report erstellen - sehe ich es richtig, dass nun allerdings nur die ersten 100 trades berücksichtig werden - die Zahlen also nichtssagend sind wenn ich ~500 trades hatte?

2) Habe Daten von Kraken importiert. Kraken hat irgendwann automatisch DAO tokens on ETH umgewandelt. Das scheint allerdings im Programm verloren gegangen zu sein. Ich vermute ich müsste also manuell einen "trade" DAO -> ETH hinzufügen, richtig?

Schließlich eine generelle Frage: Es sieht so aus also ob das Programm schon eine enorme Hilfe beim Erstellen des Steuerberichts ist - doch aber noch viele keine manuell Nacharbeit nötig ist. Gibt es inzwischen Steueranwälte/berater denen man einfach nur Zugriff auf alle Rohdaten geben kann und die alles weitere für einen machen?
Post
Topic
Board Announcements (Altcoins)
Re: Gnosis - the decentralized prediction market platform and oracle standard
by
koeppelmann
on 15/04/2017, 21:47:45 UTC
Yes - of course - there are a bunch of good reasons for this structure - we listed them here:
https://blog.gnosis.pm/why-so-complicated-ddff533c5620
Post
Topic
Board Announcements (Altcoins)
Re: Gnosis - the decentralized prediction market platform and oracle standard
by
koeppelmann
on 15/04/2017, 17:21:37 UTC
No, sorry.
Post
Topic
Board Announcements (Altcoins)
Re: Gnosis - the decentralized prediction market platform and oracle standard
by
koeppelmann
on 15/04/2017, 10:41:00 UTC
find a list of basic informations here:
https://blog.gnosis.pm/a-short-overview-of-the-gnosis-token-auction-10288a07135f

Up to 9M out of 10M tokens are offered for sale. However - we will sell them in an auction to those who bid the most - so it is possible that we will sell less then 9M tokens IF we reach the cap of $12.5M earlier.

Find a sales schedule here:
https://docs.google.com/spreadsheets/u/1/d/1vYjDat8wLd97pEfrdkzOcHd5ZLOlYjpDSkJaTnEDe1E/edit#gid=0
Post
Topic
Board Announcements (Altcoins)
Re: Gnosis - the decentralized prediction market platform and oracle standard
by
koeppelmann
on 06/04/2017, 22:51:53 UTC
sorry, the only bounty we did and will do is a bug bounty program:
https://blog.gnosis.pm/gnosis-bug-bounty-program-ce568bf4b65c
Post
Topic
Board Announcements (Altcoins)
Re: Gnosis - the decentralized prediction market platform and oracle standard
by
koeppelmann
on 05/04/2017, 18:48:54 UTC
We are happy to announce the start of the auction for April 24th.

Check out the new information on our site: gnosis.pm

A few articles writing about it:
http://www.coindesk.com/ethereum-prediction-market-project-gnosis-sets-ico-launch-date/
http://www.ibtimes.co.uk/ethereum-based-gnosis-chooses-dutch-auction-style-ico-1615562

For detailed information about Gnosis our whitepaper is the best resource: https://gnosis.pm/resources/default/pdf/gnosis_whitepaper.pdf

Let us know if you have questions.
Post
Topic
Board Announcements (Altcoins)
Re: Gnosis - the decentralized prediction market platform and oracle standard
by
koeppelmann
on 17/03/2017, 21:13:17 UTC
> What are your long term plans for Gnosis and how long of a timescale is it? Because if your funding runs out before reaching your long term plans, how are you going to raise money again?

If we reach our sale cap (~$12M) we will have a very solid runway of at least 3+ years. However - a basic version of the Gnosis platform is already live TODAY (admin.gnosis.pm). So our goal is to build the platform as strong as possible. However - if we should ever run out of funding we will still have the option to have continue with a specific project that will be build atop of the platform. This application would have its own business model (additional fee, trading spread, ads, ...) but would also pay the "base fee" to the platform.

> Another issue for me is, wouldnt it be a problem for Gnosis if Ethereum doesnt solve its scaling problem? Would you be interested in building your platform on ETC instead if they have a better scaling solution?

Let me refer to this answer:
https://forum.gnosis.pm/t/gnosis-faq/259/12


The project looks very interesting, however reaching $12M crowdfunding seems like a very challenging target for a young project like this. From my point of view, you should consider doing more rounds of ICO instead of one with a cap of $12M. You could start with a smaller cap like $1M-$2M and after reaching certain milestones do another round of ICO so the community and ICO participants can see that you are worthy of investing money.

The range of expectations is quite high. On the one end a lot of people assume that we will sell out very quickly (and would only give a way a relatively small % of tokens - on the other end are people that do not expect us to reach the cap.)
I think there is a decent chance that we will reach the cap - in the Ethereum community the project is pretty well know. We have been actually the first (more complex) DAPP that has been live on Ethereum. We gave a live demo as early as November 2015 at the DevCon 1 in London.

But anyway - time will tell - but we would not be a prediction market if we would not have set up a market to predict the outcome of the auction Smiley
Read here how to use it: https://medium.com/@aurynmacmillan/how-to-gnosis-ed1fef085014#.nfrazmkkj
without spending real ETH, try: beta.gnosis.pm
Post
Topic
Board Announcements (Altcoins)
Re: Gnosis - the decentralized prediction market platform and oracle standard
by
koeppelmann
on 17/03/2017, 21:03:31 UTC
If we reach our sale cap (~$12M) we will have a very solid runway of at least 3+ years. However - a basic version of the Gnosis platform is already live TODAY (admin.gnosis.pm).

so this is just testning site, right? not close to the real one?

Yes - this is A VERY EARLY version - but on smart contract level it is already quite sophisticated. The UI/UX is of course horrible. However - the goal of Gnosis is to offer a general platform/framwork for prediction market applications.

The applications can range from sportsbetting, over financial markets to insurances. Each of them will have a UI/UX tailored to the specific need of that app.

Get an idea of how apps will look like:
https://gnosis.pm/apps
https://www.docdroid.net/5hJGz4o/gnosis-travel.pdf.html
https://www.docdroid.net/eihMsvA/gnosis-sport.pdf.html
Post
Topic
Board Announcements (Altcoins)
Re: Gnosis - the decentralized prediction market platform and oracle standard
by
koeppelmann
on 15/03/2017, 13:10:50 UTC
> What are your long term plans for Gnosis and how long of a timescale is it? Because if your funding runs out before reaching your long term plans, how are you going to raise money again?

If we reach our sale cap (~$12M) we will have a very solid runway of at least 3+ years. However - a basic version of the Gnosis platform is already live TODAY (admin.gnosis.pm). So our goal is to build the platform as strong as possible. However - if we should ever run out of funding we will still have the option to have continue with a specific project that will be build atop of the platform. This application would have its own business model (additional fee, trading spread, ads, ...) but would also pay the "base fee" to the platform.

> Another issue for me is, wouldnt it be a problem for Gnosis if Ethereum doesnt solve its scaling problem? Would you be interested in building your platform on ETC instead if they have a better scaling solution?

Let me refer to this answer:
https://forum.gnosis.pm/t/gnosis-faq/259/12
Post
Topic
Board Announcements (Altcoins)
Re: Gnosis - the decentralized prediction market platform and oracle standard
by
koeppelmann
on 14/03/2017, 14:49:08 UTC
Hey guys - I am one of the founders of the project. Although it has been a bit quite here the project is very much alive, with a growing team and a token auction coming up soon.

We are mainly active in our slack: slack.gnosis.pm, the subreddit: reddit.com/r/gnosisPM/
Here is a good overview about the current state of the project: https://www.reddit.com/r/gnosisPM/comments/5t36om/gnosis_faq/

You can find more content about Gnosis on our blog: https://blog.gnosis.pm/ - however, if there is demand we will include this thread as well into the list of places where you can get recent updates.

Ping me here if you have questions!
Post
Topic
Board Armory
Re: Armory - Discussion Thread
by
koeppelmann
on 18/08/2015, 21:07:51 UTC
It is thread 5:

Code:
Thread 5 Crashed:
0   _CppBlockUtils.so              0x0000000104e3a3c6 StoredHeadHgtList::unserializeDBValue(BinaryRefReader&) + 470
1   _CppBlockUtils.so              0x0000000104e3a694 StoredHeadHgtList::unserializeDBValue(BinaryDataRef) + 52
2   _CppBlockUtils.so              0x0000000104e157b3 LMDBBlockDatabase::getStoredHeadHgtList(StoredHeadHgtList&, unsigned int) + 179
3   _CppBlockUtils.so              0x0000000104e1494e LMDBBlockDatabase::putBareHeader(StoredHeader&, bool) + 302
4   _CppBlockUtils.so              0x0000000104e94e25 Blockchain::putNewBareHeaders(LMDBBlockDatabase*) + 309
5   _CppBlockUtils.so              0x0000000104e4e131 BlockDataManager_LevelDB::loadDiskState(std::__1::function const&, bool) + 2945
6   _CppBlockUtils.so              0x0000000104ea5af2 BlockDataManagerThread::run() + 578
7   _CppBlockUtils.so              0x0000000104ea57f9 BlockDataManagerThread::thrun(void*) + 9
8   libsystem_pthread.dylib        0x00007fff91c5305a _pthread_body + 131
9   libsystem_pthread.dylib        0x00007fff91c52fd7 _pthread_start + 176
10  libsystem_pthread.dylib        0x00007fff91c503ed thread_start + 13

Ah ha. That is definitely Armory code.

So any tipps what I can do? Currently I simply can't access the funds in my Armory wallet?
Post
Topic
Board Armory
Re: Armory - Discussion Thread
by
koeppelmann
on 16/08/2015, 20:21:30 UTC
Hello. Is thread 0 the one that actually crashed? It could be a different one. The crash report will always say which one it is.

It is thread 5:

Code:
Process:               Python [9657]
Path:                  /Applications/Armory.app/Contents/MacOS/Python
Identifier:            com.armory.armory
Version:               ???
Code Type:             X86-64 (Native)
Parent Process:        ??? [1]
Responsible:           Python [9657]
User ID:               501

Date/Time:             2015-08-16 13:19:16.916 -0700
OS Version:            Mac OS X 10.10.5 (14F27)
Report Version:        11
Anonymous UUID:        0342B016-FFD5-109B-1719-DF5FD2B7FFA6

Sleep/Wake UUID:       CBCA24F7-E0BC-4954-86F2-65CC9B033F86

Time Awake Since Boot: 86000 seconds
Time Since Wake:       10000 seconds

Crashed Thread:        5

Exception Type:        EXC_BAD_ACCESS (SIGBUS)
Exception Codes:       0x000000000000000a, 0x0000000ae33c8001

VM Regions Near 0xae33c8001:
    mapped file            000000011f02f000-0000000adcead000 [ 39.0G] r--/rwx SM=PRV  /Users/USER/Library/Application Support/Armory/*
--> mapped file            0000000adcead000-0000000ae5273000 [131.8M] r--/rwx SM=PRV  /Users/USER/Library/Application Support/Armory/*
    MALLOC_LARGE           0000000ae5273000-0000000ae52f3000 [  512K] rw-/rwx SM=PRV 

Thread 0:: Dispatch queue: com.apple.main-thread
0   libsystem_kernel.dylib        0x00007fff90b614de mach_msg_trap + 10
1   libsystem_kernel.dylib        0x00007fff90b6064f mach_msg + 55
2   com.apple.CoreFoundation      0x00007fff913d4eb4 __CFRunLoopServiceMachPort + 212
3   com.apple.CoreFoundation      0x00007fff913d437b __CFRunLoopRun + 1371
4   com.apple.CoreFoundation      0x00007fff913d3bd8 CFRunLoopRunSpecific + 296
5   com.apple.HIToolbox            0x00007fff8fe2456f RunCurrentEventLoopInMode + 235
6   com.apple.HIToolbox            0x00007fff8fe242ea ReceiveNextEventCommon + 431
7   com.apple.HIToolbox            0x00007fff8fe2412b _BlockUntilNextEventMatchingListInModeWithFilter + 71
8   com.apple.AppKit              0x00007fff92b018ab _DPSNextEvent + 978
9   com.apple.AppKit              0x00007fff92b00e58 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 346
10  com.apple.AppKit              0x00007fff92af6af3 -[NSApplication run] + 594
11  QtGui                          0x00000001040d684a QEventDispatcherMac::processEvents(QFlags) + 538
12  QtCore                        0x000000010366aaad QEventLoop::exec(QFlags) + 477
13  QtCore                        0x000000010366dcc7 QCoreApplication::exec() + 199
14  QtGui.so                      0x00000001038d5a10 meth_QApplication_exec_(_object*, _object*) + 80
15  org.python.python              0x00000001000b07f6 PyEval_EvalFrameEx + 20486
16  org.python.python              0x00000001000ab57d PyEval_EvalCodeEx + 1725
17  org.python.python              0x00000001000aaeb6 PyEval_EvalCode + 54
18  org.python.python              0x00000001000d43e4 PyRun_FileExFlags + 164
19  org.python.python              0x00000001000d3f61 PyRun_SimpleFileExFlags + 769
20  org.python.python              0x00000001000eafd7 Py_Main + 3063
21  Python                        0x0000000100000e55 0x100000000 + 3669
22  Python                        0x0000000100000d71 0x100000000 + 3441

Thread 1:: Dispatch queue: com.apple.libdispatch-manager
0   libsystem_kernel.dylib        0x00007fff90b67232 kevent64 + 10
1   libdispatch.dylib              0x00007fff94516a6a _dispatch_mgr_thread + 52

Thread 2:: com.apple.CFSocket.private
0   libsystem_kernel.dylib        0x00007fff90b663fa __select + 10
1   libsystem_pthread.dylib        0x00007fff91c5305a _pthread_body + 131
2   libsystem_pthread.dylib        0x00007fff91c52fd7 _pthread_start + 176
3   libsystem_pthread.dylib        0x00007fff91c503ed thread_start + 13

Thread 3:
0   libsystem_kernel.dylib        0x00007fff90b614de mach_msg_trap + 10
1   libsystem_kernel.dylib        0x00007fff90b6064f mach_msg + 55
2   com.apple.CoreFoundation      0x00007fff913d4eb4 __CFRunLoopServiceMachPort + 212
3   com.apple.CoreFoundation      0x00007fff913d437b __CFRunLoopRun + 1371
4   com.apple.CoreFoundation      0x00007fff913d3bd8 CFRunLoopRunSpecific + 296
5   com.apple.AppKit              0x00007fff92bc956b _NSEventThread + 137
6   libsystem_pthread.dylib        0x00007fff91c5305a _pthread_body + 131
7   libsystem_pthread.dylib        0x00007fff91c52fd7 _pthread_start + 176
8   libsystem_pthread.dylib        0x00007fff91c503ed thread_start + 13

Thread 4:
0   libsystem_kernel.dylib        0x00007fff90b663fa __select + 10
1   org.python.python              0x00000001000b07f6 PyEval_EvalFrameEx + 20486
2   org.python.python              0x00000001000ab57d PyEval_EvalCodeEx + 1725
3   org.python.python              0x00000001000364dc function_call + 364
4   org.python.python              0x0000000100010ca3 PyObject_Call + 99
5   org.python.python              0x00000001000aecbd PyEval_EvalFrameEx + 13517
6   org.python.python              0x00000001000ab57d PyEval_EvalCodeEx + 1725
7   org.python.python              0x00000001000b3129 fast_function + 297
8   org.python.python              0x00000001000ae995 PyEval_EvalFrameEx + 12709
9   org.python.python              0x00000001000b30c2 fast_function + 194
10  org.python.python              0x00000001000ae995 PyEval_EvalFrameEx + 12709
11  org.python.python              0x00000001000b30c2 fast_function + 194
12  org.python.python              0x00000001000ae995 PyEval_EvalFrameEx + 12709
13  org.python.python              0x00000001000ab57d PyEval_EvalCodeEx + 1725
14  org.python.python              0x00000001000364dc function_call + 364
15  org.python.python              0x0000000100010ca3 PyObject_Call + 99
16  org.python.python              0x000000010001de16 instancemethod_call + 166
17  org.python.python              0x0000000100010ca3 PyObject_Call + 99
18  org.python.python              0x00000001000b288d PyEval_CallObjectWithKeywords + 93
19  org.python.python              0x00000001000ed1a6 t_bootstrap + 70
20  libsystem_pthread.dylib        0x00007fff91c5305a _pthread_body + 131
21  libsystem_pthread.dylib        0x00007fff91c52fd7 _pthread_start + 176
22  libsystem_pthread.dylib        0x00007fff91c503ed thread_start + 13

Thread 5 Crashed:
0   _CppBlockUtils.so              0x0000000104e3a3c6 StoredHeadHgtList::unserializeDBValue(BinaryRefReader&) + 470
1   _CppBlockUtils.so              0x0000000104e3a694 StoredHeadHgtList::unserializeDBValue(BinaryDataRef) + 52
2   _CppBlockUtils.so              0x0000000104e157b3 LMDBBlockDatabase::getStoredHeadHgtList(StoredHeadHgtList&, unsigned int) + 179
3   _CppBlockUtils.so              0x0000000104e1494e LMDBBlockDatabase::putBareHeader(StoredHeader&, bool) + 302
4   _CppBlockUtils.so              0x0000000104e94e25 Blockchain::putNewBareHeaders(LMDBBlockDatabase*) + 309
5   _CppBlockUtils.so              0x0000000104e4e131 BlockDataManager_LevelDB::loadDiskState(std::__1::function const&, bool) + 2945
6   _CppBlockUtils.so              0x0000000104ea5af2 BlockDataManagerThread::run() + 578
7   _CppBlockUtils.so              0x0000000104ea57f9 BlockDataManagerThread::thrun(void*) + 9
8   libsystem_pthread.dylib        0x00007fff91c5305a _pthread_body + 131
9   libsystem_pthread.dylib        0x00007fff91c52fd7 _pthread_start + 176
10  libsystem_pthread.dylib        0x00007fff91c503ed thread_start + 13

Thread 6:
Post
Topic
Board Altcoin Discussion
Re: Circles - The basic income currency
by
koeppelmann
on 11/08/2015, 06:27:20 UTC
The latest version of Circles can be found here:
https://ourbasicincome.wordpress.com/2015/06/18/circles-universal-basic-income/

and a place to discuss here: http://forum.aboutcircles.com/
Post
Topic
Board Armory
Re: Armory - Discussion Thread
by
koeppelmann
on 11/08/2015, 05:27:11 UTC
Thanks for the response. I build the Bitcoin BD again but I still have the problem. I can not use Armory at all - while starting it always crashes.

It seems that you are and the problem is related to QT:

Code:
Thread 0:: Dispatch queue: com.apple.main-thread
0   libsystem_kernel.dylib        0x00007fff873074de mach_msg_trap + 10
1   libsystem_kernel.dylib        0x00007fff8730664f mach_msg + 55
2   com.apple.CoreFoundation      0x00007fff8f6b4eb4 __CFRunLoopServiceMachPort + 212
3   com.apple.CoreFoundation      0x00007fff8f6b437b __CFRunLoopRun + 1371
4   com.apple.CoreFoundation      0x00007fff8f6b3bd8 CFRunLoopRunSpecific + 296
5   com.apple.HIToolbox            0x00007fff8df3d56f RunCurrentEventLoopInMode + 235
6   com.apple.HIToolbox            0x00007fff8df3d2ea ReceiveNextEventCommon + 431
7   com.apple.HIToolbox            0x00007fff8df3d12b _BlockUntilNextEventMatchingListInModeWithFilter + 71
8   com.apple.AppKit              0x00007fff8a7578ab _DPSNextEvent + 978
9   com.apple.AppKit              0x00007fff8a756e58 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 346
10  com.apple.AppKit              0x00007fff8a74caf3 -[NSApplication run] + 594
11  QtGui                          0x00000001040d684a QEventDispatcherMac::processEvents(QFlags) + 538
12  QtCore                        0x000000010366aaad QEventLoop::exec(QFlags) + 477
13  QtCore                        0x000000010366dcc7 QCoreApplication::exec() + 199
14  QtGui.so                      0x00000001038d5a10 meth_QApplication_exec_(_object*, _object*) + 80
15  org.python.python              0x00000001000b07f6 PyEval_EvalFrameEx + 20486
16  org.python.python              0x00000001000ab57d PyEval_EvalCodeEx + 1725
17  org.python.python              0x00000001000aaeb6 PyEval_EvalCode + 54
18  org.python.python              0x00000001000d43e4 PyRun_FileExFlags + 164
19  org.python.python              0x00000001000d3f61 PyRun_SimpleFileExFlags + 769
20  org.python.python              0x00000001000eafd7 Py_Main + 3063
21  Python                        0x0000000100000e55 0x100000000 + 3669
22  Python                        0x0000000100000d71 0x100000000 + 3441

Yes, I do use the sleep function often - basically always, I never shut my mac down. But i also started to restart it, start BitcoinQt, start Amory -> same problem.
Post
Topic
Board Armory
Re: Armory - Discussion Thread
by
koeppelmann
on 02/08/2015, 05:49:08 UTC
My armory breaks down every time I start it. Or better: as soon as it is connected to BitcoinQT (while organziing blockchain). I have the latest version of BitcoinQT and Armory. It was everything ok for weeks. But today it happend EVERY time (I tired at least 10 times, reboot, ...) I have a mac.

Any hint what I should do? Rebuilt blockchain? Reinstall Armory?

Those are the first lines of the error report:

rocess:               Python [822]
Path:                  /Applications/Armory.app/Contents/MacOS/Python
Identifier:            com.armory.armory
Version:               Huh
Code Type:             X86-64 (Native)
Parent Process:        Huh [1]
Responsible:           Python [822]
User ID:               501

Date/Time:             2015-08-01 22:47:16.836 -0700
OS Version:            Mac OS X 10.10.4 (14E46)
Report Version:        11
Anonymous UUID:        0342B016-FFD5-109B-1719-DF5FD2B7FFA6

Sleep/Wake UUID:       A3F7E20C-0AA7-44AD-8CD9-7D44B0AF6A3F

Time Awake Since Boot: 2400 seconds
Time Since Wake:       1300 seconds

Crashed Thread:        8

Exception Type:        EXC_BAD_ACCESS (SIGBUS)
Exception Codes:       0x000000000000000a, 0x0000000ae461e001

VM Regions Near 0xae461e001:
    MALLOC_LARGE           0000000adde02000-0000000ade103000 [ 3076K] rw-/rwx SM=PRV 
--> mapped file            0000000ade103000-0000000ae64c9000 [131.8M] r--/rwx SM=PRV  /Users/USER/Library/Application Support/Armory/*
    MALLOC_LARGE           0000000ae64c9000-0000000ae67ca000 [ 3076K] rw-/rwx SM=PRV 

Thread 0:: Dispatch queue: com.apple.main-thread
0   libdispatch.dylib                0x00007fff8b59f7f8 _dispatch_queue_wakeup_with_qos_slow + 1075
1   com.apple.coreui                 0x00007fff8d155bed PerformBlockWithThemeRegistry + 102
2   com.apple.coreui                 0x00007fff8d155e7e _LookupThemeProvider + 232
3   com.apple.coreui                 0x00007fff8d1391e1 -[CUIThemeFacet _approximateRenditionForRenditionKey:] + 109
4   com.apple.coreui                 0x00007fff8d13e706 -[CUIThemeFacet imageSize] + 83
Post
Topic
Board Altcoin Discussion
Topic OP
Circles - The basic income currency
by
koeppelmann
on 13/06/2015, 03:10:30 UTC
"Circles" will be a currency created from basic incomes only. In the system outlined in the following, new money is constantly distributed to every account participating in the system. The money in every individual account are uniquely identifiyable and only gain in value if the account connects to other accounts and joins groups. This incentivizes every user to limit themself to one account.

latest project draft here: http://piratepad.net/kjTwIzn5u3
  • 1 Everyone can create a new account
  • 2 An account will constantly generate an income (1000 units per week)
  • 3 The rate at which the income is generated will increase by g=2% per year
  • 4 A new account starts with the income that will be generated in the next 3 months
  • 5 One month of income is for the account owner - the other two are reserverd for people who trust this account, it is called the trustee reward.
  • 6 Accounts can trust one another. This will allow both accounts holders to exchange their coins 1:1.
  • 7 Trust can be revoked by both parties.
  • 8 If an account trusts another account it is credited with half of the remaining trustee reward.
  • 9 Arbitrary groups can be created.
  • 10 Groups can verify accounts as members.
  • 11 Groups can exclude accounts as members.
  • 12 All members can convert their private money into group money (1:1 exchange rate). This exchange is irreversible.

The easiest way to implement this would be as contracts on ethereum:
Code:
//data structure
Dictionary -> tuple
accounts[owner] =  (time_created, money_spent, trustee_reward)
Dictionary -> Set
groups[owner] =  [member1, member2 ,..]
Dictionary -> Set
trustees[account] = [account1, account2, ...] // each relationship need only be saved once
Dictionary - > Dictionary -> int
balance[owner][foreign_account] = amount
Int
years = 0

//pseudo code

create_account():
    trustee_reward = (1000*12) * 1.02 ** years
    accounts[message.sender] = (block.time - 1month, 0, trustee_reward)

add_account(account1, account2):
    //somehow check that both accounts signed the message
    if int(account1) > int(acount2):
        trustees[account1].append(account2)
    else:
        trustees[account2].append(account1)
    //credit and update the trustee reward
    balance[account1][account2] = accounts[account2][3] / 2
    balance[account2][account1] = accounts[account1][3] / 2
    accounts[account2][3] /= 2
    accounts[account1][3] /= 2   

revoke_trust(account):
    if int(message.sender) > account:
        trustees[message.sender].remove(account)
    else:
        trustees[account].remove(message.sender)

send_money(amount, currency, receiver):
    if balance[message.sender][currency] >= amount:
        balance[message.sender][currency] -= amount
        balance[receiver][currency] += amount

send_new_income(receiver, amount):
        //todo factor in 2% growth rate
        income_generated = (block.time - accounts[message.sender][0])/ weeks * 1000
        if income_generated - money_spent > amount:
            money_spent += amount
            balance[receiver][currency] += amount

exchange_money(account1, account2, amount)
    if message.sender == account1 or message.sender == account2:
        if account2 in trustees[account1]:
            if balance[account1][account1] >= amount:
                if balance[account2][account2] >= amount:
                    balance[account1][account1] -= amount
                    balance[account2][account2] -= amount
                    balance[account1][account2] += amount
                    balance[account2][account1] += amount

create_group()
    groups[message.sender] = Set()

add_group_member(account)
    groups[message.sender].add(account)

remove_groupt_member(account)
    groups[message.sender].remove(account)

convert_into_group_money(group, amount)
    if message.sender in groups[group]:
        if amounts[message.sender][message.sender] >= amount:
           amounts[message.sender][message.sender] -= amount
           amounts[message.sender][group] += amount
Design rationale
The main purpose of this project is to establish a world wide basic income.

Requirements are:
a. Decentralization
A world wide basic income is something so powerful that no single entity in the world should have control over it in order to preclude manipulation. Particularly, there should be no central authority that desicdes which person can get a basic income and which person cannot.

b. Smooth growth
The solution should support a smooth growth. If the only two equilibria are "no one participates" or "all people participate" then it is nearly impossible to change to the "all" equilibrium, especially if no central entity is involved. In the approach presented here, groups can grow locally, even starting at a single family level. However, there are no constraints on subsystem growth. All subsystems can merge into a global system at any time.

c. Resilliance
The system can support something like a world currency. However - if this currency fails at some point, it is not the whole system that would collapse. Instead, the system would fall back on the group level underneath, for instance a country group. Even if the group currencies should fail at one point (because they accepted too many memerbs that just consume their income and don't provide any goods or services for their income) it can still fall back on the personal level where the value of a currency is closely related to the personal relationship with the other person.

d. Incentives for organic growth
The trust reward should help to give a strong incentive to bring new people to the system. Adding new accounts to your circle is to some degree a risk. To balance the incentives and enable growth we introduced the trust reward. It creates common incentives for both the newcomer and the people already established in the network: Through the acknowledgment of the trust relationship, the newcomer gains network credibility and the first people to place their trust in the newcomer benefit financially. The risk inherent to trusting a newcomer are only outweight by the benefits if the newcomer is beknown to the people who place their trust in them. If the newcomer does not turn into a viable member of the network the trust placed in the newcomer was misguided and the trust results in a financial loss.



e. Universality
Some people argue that Bitcoin was a one time shot. A currency has to be scarce to some degree to function as such. A single digital currency can have features that ensures the scarcity of this currency - however, if other digital currencies become successful, scarcity as a characteristic of digitial currencies overall becomes questionable. This is especially true for a basic income. We strongly believe that a basic income currency can only be successful if it is the only one that is commonly used. This is why we keep this proposal as general as possible. The only free parameter crucial to the system is the growth rate g and needs to be discussed carefully. The trust reward is not strictly necessary, however, it does not affect the long term equilibria of this approach.



Detailed discussion.

6:
Transitive Transactions
If A and B trust each other, and B and C trust each other, then A and C can pay each other as long as B is liquid. If A is a customer and C is a merchant, A could send money to C. The network will automatically send a-coins from A to B and b-coins in exchange for the a-coinsfrom B to C.


3:
The growth rate g = 2%.
The growth rate g determines the ratio between the total coin supply and the income per month. This number is subject to discussion. It should be chosen to maximize the value of the income.
Note that a high growth rate (inflation rate) destroys the capability of the currency as a store of value. Consequently, the potential dollar market cap is a function of the growth rate: market cap = f(g). (The market cap of the currency is a function of g that most likely will decrease sharply for bigger g like 5% or 10%). g should be chosen to maximize g*f(g).

The growth rate can be seen as a capital tax that finances the basic income. People with exactly the average wealth would pay the same amount of money in fees as they would get from their UBI.

9-12:
Groups
Groups are necessary to bring more stability into the system. Holding coins of a specific person always carries a certain risk. In some sense, the value of theses coins is always backed by the person. If the person dies or more broadly speaking the trust in this person sinks, these coins may become worthless. However, as long as a person is member of a group, the money can be converted irreversibly into group money. It is in the responsibility of the groups themselves to keep them tight on the one hand to not dilute the value, but on the other hand have a positive network effect. This makes it interesting for merchants to accept such group money.




FAQ:
Q: Can I create 100 fake accounts that all trust each other and abuse the system?
A: You can create them but this will not create value. As long as nobody else trusts these accounts they can only exchange money with each other, rendering all the money worthless.


Q: Why should I add someone else to my trust network?
A. Your trust network is what gives your personall currency value beyond what you are willing to provide for this currency. Lets say 100 people are in your trust network, that means that 100 people are accepting your currency. Even for those who do not accept your currency directly, may accept it indirectly since they know they can use it to get goods or services from 100 people. Accepting money is all about network effects.
However, on the other hand accepting a new person bears some risk. If this person turns out to be a fake account you will end up having his worthless money and the scammer can spend your money. To make the incentive higher to be among the first to accept an new account nevertheless, the trustee reward was introduced. However, accepting a completely new account will and should be backed by a personal relationship of the two participants that ensures that the new person participates honestly in the system. If they don't the only person who loses money is the person who wrongly trusted them.



Q: What is the money of an account worth?
A: In theory it should be max(value(group1), value(group2), value(group3), ... , value(connection1), value(connection2), ...). Note that only connections to liquid people count. As long as the memberships in the groups and the connections are stable (or expected to be stable) there should be no incentive to convert money into group money.
This concludes in the assumption that it is not necessary to convert your money into group money or to exchange money with one of your trusted connections. Just having the ability to do so makes your money at least as worthy. This could stabilize the system and allow user A to connect to user B despite the fact that user B's coins are worth less. This connection could raise the value of user B's coins without changing the value of A's coins. However, this stops if B tries to abuse this connection, but in this case, A can cancel the trust relationship.
From time to time users could lose their connections because they create panic. This is the unliklier the better the user is connected. This strengthens the incentive to concentrate all your social connections/ reputation into one accout.

Q: How much of the group money is yours?
A: The amount that you've converted. Only difference is that now it's no longer tied to you as an individiual. This means that if you do something bad, the group cannot do anything to revoke your group money. However, they can kick you out of the group.

With groups exchanges are mono directional with individuals. Only individual => group, NOT group => individual. However, exchanges are is bi-directional between groups. So Berlin <=> SF is OK.