Dear all,

I'm new.

Please, can someone else teach me how to find out my stat with protoshare mining?

Thanks and appreciate for your help.

which pool are you mining with?

Mobile apps tend to be convinient for most users as we always tend to be on the move. I hate apple but if they allowed such apps i would buy one this instant, apple is far more secure than android and they may end up missing out on the train as more apps are developed bringing crypto to the world. I think it has something to do with their trying to make their own currency, i however thing it's a fail as it may be limited to apple products and services whereas other cryptos aim to be globaly used in any way possible.

Will the consensus be amended or will it maintain the difference between AGS funded DAC vs 3rd party DAC?

Is that the final version all round or just for Bitshares?

I made a few modifications to add coin control to the client but it now refuses to compile i get this error:-

cd /home/barwizi/memorycoin-psforkinit/memorycoin-psforkinit; /bin/sh share/genbuild.sh /home/barwizi/memorycoin-psforkinit/memorycoin-psforkinit/build/build.h
fatal: Not a git repository (or any of the parent directories): .git
/usr/lib/x86_64-linux-gnu/qt4/bin/uic src/qt/forms/sendcoinsdialog.ui -o build/ui_sendcoinsdialog.h
/usr/lib/x86_64-linux-gnu/qt4/bin/uic src/qt/forms/addressbookpage.ui -o build/ui_addressbookpage.h
/usr/lib/x86_64-linux-gnu/qt4/bin/uic src/qt/forms/signverifymessagedialog.ui -o build/ui_signverifymessagedialog.h
/usr/lib/x86_64-linux-gnu/qt4/bin/uic src/qt/forms/aboutdialog.ui -o build/ui_aboutdialog.h
/usr/lib/x86_64-linux-gnu/qt4/bin/uic src/qt/forms/editaddressdialog.ui -o build/ui_editaddressdialog.h
/usr/lib/x86_64-linux-gnu/qt4/bin/uic src/qt/forms/transactiondescdialog.ui -o build/ui_transactiondescdialog.h
/usr/lib/x86_64-linux-gnu/qt4/bin/uic src/qt/forms/overviewpage.ui -o build/ui_overviewpage.h
/usr/lib/x86_64-linux-gnu/qt4/bin/uic src/qt/forms/sendcoinsentry.ui -o build/ui_sendcoinsentry.h
/usr/lib/x86_64-linux-gnu/qt4/bin/uic src/qt/forms/askpassphrasedialog.ui -o build/ui_askpassphrasedialog.h
/usr/lib/x86_64-linux-gnu/qt4/bin/uic src/qt/forms/rpcconsole.ui -o build/ui_rpcconsole.h
/usr/lib/x86_64-linux-gnu/qt4/bin/uic src/qt/forms/optionsdialog.ui -o build/ui_optionsdialog.h
/usr/lib/x86_64-linux-gnu/qt4/bin/uic src/qt/forms/votecoinsdialog.ui -o build/ui_votecoinsdialog.h
/usr/lib/x86_64-linux-gnu/qt4/bin/uic src/qt/forms/votecoinsentry.ui -o build/ui_votecoinsentry.h
g++ -c -m64 -pipe -fstack-protector-all -D_FORTIFY_SOURCE=2 -O2 -D_REENTRANT -fdiagnostics-show-option -Wall -Wextra -Wformat -Wformat-security -Wno-unused-parameter -Wstack-protector -DQT_GUI -DBOOST_THREAD_USE_LIB -DBOOST_SPIRIT_THREADSAFE -DSCRYPT_CHACHA -DSCRYPT_KECCAK512 -DUSE_UPNP=1 -DSTATICLIB -DUSE_IPV6=1 -DHAVE_BUILD_INFO -DLINUX -D_FILE_OFFSET_BITS=64 -DQT_NO_DEBUG -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtNetwork -I/usr/include/qt4/QtGui -I/usr/include/qt4 -Isrc -Isrc/json -Isrc/qt -Isrc/leveldb/include -Isrc/leveldb/helpers -Ibuild -Ibuild -o build/bitcoin.o src/qt/bitcoin.cpp
In file included from src/wallet.h:13:0,
                 from src/init.h:8,
                 from src/qt/bitcoin.cpp:13:
src/main.h:616:11: error: default argument missing for parameter 2 of ‘int64 CTransaction::GetMinFee(unsigned int, unsigned int, bool, GetMinFee_mode) const’
make: *** [build/bitcoin.o] Error 1
barwizi@barwizi-dev:~/memorycoin-psforkinit/memorycoin-psforkinit$
anyone got an idea?

https:github.com/Nameshar/memorycoin

Quote from: barwizi on January 28, 2014, 07:39:45 am

Your small DAC at the beginning allocates 10% of it's equity to PTS,  the effect is right at the beginning, you already have thousands of possible customers willing to purchase your services. It is also meant as a mechanism that with good management and application can secure a "stable" base price for equity units. The relationship goes both ways, by raising good value on your equity, it will help PTS rise, but also, when PTS rises so does your equity value.

III software is anything developed by them, bounties or otherwise paid for by them. Use of the software includes but is not limited to running it as it is, making modifications and forking.

Great answer - thanks a lot

When you think of PTS / DACs in a "total economy" sense - "user" has many different meanings. I think you wiggled around the one member class I was looking for...which I think is good.

3rd party (non-I3) software which uses/interfaces with I3 software without modification to I3 code, seem...exempt?  (Did I just describe a DAC in legal-ese?)

They could probly go around PTS / use another currency /etc. But wouldn't want to depending on stability / timeframe / etc like you said - and access to network of PTS individuals / reputation / etc.

3rd party (non-I3) software which uses/interfaces with I3 software without modification to I3 code, seem...exempt?  (Did I just describe a DAC in legal-ese?)

that is correct, since they are not modifying the actual code.

They could probly go around PTS / use another currency /etc. But wouldn't want to depending on stability / timeframe / etc like you said - and access to network of PTS individuals / reputation / etc.

yes you can create A DAC  with other code, but you would be hard pressed on the dev side since that means you have to do everything  yourself, none of the improvements offered here will apply to you.

this is a bit complicated and i tried finding info on ripple but it ain't out there. if anyone has coding time do the following create a system with defined security check points, say we have "security nodes" , a transaction can only be created when connected to at least two "security nodes".  Once a transaction is made it is transmitted through the network and only confirmed when all security nodes have consensus.

To avoid Ddos issues, security nodes are not permanent, they could be any machine in the network. this is how it will function:-

1) at any given time there are ten security nodes each is in possession of a token that verifies it's designation. After a certain number of blocks/transactions the tokens are passed to another machine on the network. If a machine with a token goes offline, one of the others will generate and pass on two tokens on the next round to cover for the lost one. further, timers are place on network activity of each node keeping record of how many transactions it has transmitted and how many times it has been in possession of a token This is then used for trust ratings in the event of a fork, such modification can be done in 24hrs to the BTC code.

Maybe instead of "buy PTS", I should have said "invest" or "want to buy services or goods" with it...a combination of savings power and purchasing power...fundamental value.

Can you explain the financial relationships / effects of the license to "small DACs" or start-up web services...maybe like an ebay start-up seller or micro-blogger site?

E.g., what do you mean by "I3 software" and "use the software"?  Do you mean "developed by I3 in the future" / "fork the code"?

either way, if all you do is use the units without the code then you need not worry about the license. those that make direct use of the software and/or want to fork/modify however have to worry about their position.

I think what you want to know is if holding PTS gives you legal standing, III intends to give such legal standing. I am working on how to put that in legalese so expect the update in a few hours.

Your small DAC at the beginning allocates 10% of it's equity to PTS,  the effect is right at the beginning, you already have thousands of possible customers willing to purchase your services. It is also meant as a mechanism that with good management and application can secure a "stable" base price for equity units. The relationship goes both ways, by raising good value on your equity, it will help PTS rise, but also, when PTS rises so does your equity value.

III software is anything developed by them, bounties or otherwise paid for by them. Use of the software includes but is not limited to running it as it is, making modifications and forking.