Also to help make sense of it here are the code sections which are apparently conflicting: // *** Begin of Berkeley DB Snippet ***:
// db.h:
/*
* Berkeley DB version information.
*/
#define DB_VERSION_MAJOR 4
#define DB_VERSION_MINOR 8
#define DB_VERSION_PATCH 30
#define DB_VERSION_STRING "Berkeley DB 4.8.30: (April 12, 2010)"
/*
* !!!
* Berkeley DB uses specifically sized types. If they're not provided by
* the system, typedef them here.
*
* We protect them against multiple inclusion using __BIT_TYPES_DEFINED__,
* as does BIND and Kerberos, since we don't know for sure what #include
* files the user is using.
*
* !!!
* We also provide the standard u_int, u_long etc., if they're not provided
* by the system.
*/
#ifndef __BIT_TYPES_DEFINED__
#define __BIT_TYPES_DEFINED__
typedef unsigned char u_int8_t;
typedef short int16_t;
typedef unsigned short u_int16_t;
typedef int int32_t;
typedef unsigned int u_int32_t;
typedef __int64 int64_t;
typedef unsigned __int64 u_int64_t;
#endif
#ifndef _WINSOCKAPI_
typedef unsigned char u_char;
typedef unsigned int u_int;
typedef unsigned long u_long;
#endif
typedef unsigned short u_short;
/*
* Missing ANSI types.
*
* uintmax_t --
* Largest unsigned type, used to align structures in memory. We don't store
* floating point types in structures, so integral types should be sufficient
* (and we don't have to worry about systems that store floats in other than
* power-of-2 numbers of bytes). Additionally this fixes compilers that rewrite
* structure assignments and ANSI C memcpy calls to be in-line instructions
* that happen to require alignment.
*
* uintptr_t --
* Unsigned type that's the same size as a pointer. There are places where
* DB modifies pointers by discarding the bottom bits to guarantee alignment.
* We can't use uintmax_t, it may be larger than the pointer, and compilers
* get upset about that. So far we haven't run on any machine where there's
* no unsigned type the same size as a pointer -- here's hoping.
*/
#if defined(_MSC_VER) && _MSC_VER < 1300
typedef u_int32_t uintmax_t;
#else
typedef u_int64_t uintmax_t;
#endif
#ifdef _WIN64
typedef u_int64_t uintptr_t;
#else
typedef u_int32_t uintptr_t;
#endif
/*
* Windows defines off_t to long (i.e., 32 bits). We need to pass 64-bit
* file offsets, so we declare our own.
*/
#define off_t __db_off_t
typedef int64_t off_t;
typedef int pid_t;
#ifdef _WIN64
typedef int64_t ssize_t;
#else
typedef int32_t ssize_t;
#endif
// *** End of Berkeley DB Snippet ***
// *** Begin of MingW Snippet ***:
// types.h:
#ifndef _SSIZE_T_
#define _SSIZE_T_
typedef long _ssize_t;
#ifndef _NO_OLDNAMES
typedef _ssize_t ssize_t;
#endif
#endif /* Not _SSIZE_T_ */
// *** End of MingW Snippet ***
Please advise... |
|
|
|
Hello, Building the bitcoin-qt 0.5.0rc7 client for win32 (on windows 7) has a little problem, qtcreator reports a conflicting type "ssize_t". So two simple questions I guess: 1. How many bits should ssize_t be for mingw32 (types.h) ? 2. How many bits should ssize_t be for berkeley db (db.h) ? And finally: 3. What would be a good solution to fix it ? (I could rename the type in db.h and modify all source code of berkeley db, but maybe there is an easier way ? Also I am not sure if renaming the type would help, since maybe there is a size conflict as well, hence questions 1 and 2 to be sure... ) Running build steps for project skycoin-qt...
Starting: "C:\Tools\QtSDK\mingw\bin\mingw32-make.exe" clean
C:/Tools/QtSDK/mingw/bin/mingw32-make -f Makefile.Debug clean
mingw32-make[1]: Entering directory `X:/CPP/Applications/SkyCoin/version 0.02 complete try the qt creator with the pro file/skycoin-qt-build-desktop-Qt_4_7_4_for_Desktop_-_MinGW_4_4__Qt_SDK__Debug'
del src\qt\locale\bitcoin_da.qm src\qt\locale\bitcoin_de.qm src\qt\locale\bitcoin_en.qm src\qt\locale\bitcoin_es.qm src\qt\locale\bitcoin_es_CL.qm src\qt\locale\bitcoin_nb.qm src\qt\locale\bitcoin_nl.qm src\qt\locale\bitcoin_ru.qm src\qt\locale\bitcoin_zh_TW.qm
del build\moc_bitcoingui.cpp build\moc_transactiontablemodel.cpp build\moc_addresstablemodel.cpp build\moc_optionsdialog.cpp build\moc_sendcoinsdialog.cpp build\moc_addressbookpage.cpp build\moc_aboutdialog.cpp build\moc_editaddressdialog.cpp build\moc_bitcoinaddressvalidator.cpp build\moc_clientmodel.cpp build\moc_optionsmodel.cpp build\moc_monitoreddatamapper.cpp build\moc_transactiondesc.cpp build\moc_transactiondescdialog.cpp build\moc_bitcoinamountfield.cpp build\moc_transactionfilterproxy.cpp build\moc_transactionview.cpp build\moc_walletmodel.cpp build\moc_overviewpage.cpp build\moc_csvmodelwriter.cpp build\moc_sendcoinsentry.cpp build\moc_qvalidatedlineedit.cpp build\moc_qvaluecombobox.cpp build\moc_askpassphrasedialog.cpp build\moc_notificator.cpp
del debug\qrc_bitcoin.cpp
del build\optionsdialog.moc build\overviewpage.moc
Could Not Find X:\CPP\Applications\SkyCoin\version 0.02 complete try the qt creator with the pro file\skycoin-qt-build-desktop-Qt_4_7_4_for_Desktop_-_MinGW_4_4__Qt_SDK__Debug\src\qt\locale\bitcoin_da.qm
Could Not Find X:\CPP\Applications\SkyCoin\version 0.02 complete try the qt creator with the pro file\skycoin-qt-build-desktop-Qt_4_7_4_for_Desktop_-_MinGW_4_4__Qt_SDK__Debug\build\moc_bitcoingui.cpp
Could Not Find X:\CPP\Applications\SkyCoin\version 0.02 complete try the qt creator with the pro file\skycoin-qt-build-desktop-Qt_4_7_4_for_Desktop_-_MinGW_4_4__Qt_SDK__Debug\debug\qrc_bitcoin.cpp
del build\ui_sendcoinsdialog.h build\ui_addressbookpage.h build\ui_aboutdialog.h build\ui_editaddressdialog.h build\ui_transactiondescdialog.h build\ui_overviewpage.h build\ui_sendcoinsentry.h build\ui_askpassphrasedialog.h
del build\bitcoin.o build\bitcoingui.o build\transactiontablemodel.o build\addresstablemodel.o build\optionsdialog.o build\sendcoinsdialog.o build\addressbookpage.o build\aboutdialog.o build\editaddressdialog.o build\bitcoinaddressvalidator.o build\util.o build\script.o build\main.o build\init.o build\net.o build\irc.o build\db.o build\json_spirit_writer.o build\json_spirit_value.o build\json_spirit_reader.o build\clientmodel.o build\guiutil.o build\transactionrecord.o build\optionsmodel.o build\monitoreddatamapper.o build\transactiondesc.o build\transactiondescdialog.o build\bitcoinstrings.o build\bitcoinamountfield.o build\wallet.o build\keystore.o build\transactionfilterproxy.o build\transactionview.o build\walletmodel.o build\bitcoinrpc.o build\overviewpage.o build\csvmodelwriter.o build\crypter.o build\sendcoinsentry.o build\qvalidatedlineedit.o build\bitcoinunits.o build\qvaluecombobox.o build\askpassphrasedialog.o build\protocol.o build\notificator.o build\moc_bitcoingui.o build\moc_transactiontablemodel.o build\moc_addresstablemodel.o build\moc_optionsdialog.o build\moc_sendcoinsdialog.o build\moc_addressbookpage.o build\moc_aboutdialog.o build\moc_editaddressdialog.o build\moc_bitcoinaddressvalidator.o build\moc_clientmodel.o build\moc_optionsmodel.o build\moc_monitoreddatamapper.o build\moc_transactiondesc.o build\moc_transactiondescdialog.o build\moc_bitcoinamountfield.o build\moc_transactionfilterproxy.o build\moc_transactionview.o build\moc_walletmodel.o build\moc_overviewpage.o build\moc_csvmodelwriter.o build\moc_sendcoinsentry.o build\moc_qvalidatedlineedit.o build\moc_qvaluecombobox.o build\moc_askpassphrasedialog.o build\moc_notificator.o build\qrc_bitcoin.o
del build\bitcoin-qt_res.o
mingw32-make[1]: Leaving directory `X:/CPP/Applications/SkyCoin/version 0.02 complete try the qt creator with the pro file/skycoin-qt-build-desktop-Qt_4_7_4_for_Desktop_-_MinGW_4_4__Qt_SDK__Debug'
C:/Tools/QtSDK/mingw/bin/mingw32-make -f Makefile.Release clean
mingw32-make[1]: Entering directory `X:/CPP/Applications/SkyCoin/version 0.02 complete try the qt creator with the pro file/skycoin-qt-build-desktop-Qt_4_7_4_for_Desktop_-_MinGW_4_4__Qt_SDK__Debug'
del src\qt\locale\bitcoin_da.qm src\qt\locale\bitcoin_de.qm src\qt\locale\bitcoin_en.qm src\qt\locale\bitcoin_es.qm src\qt\locale\bitcoin_es_CL.qm src\qt\locale\bitcoin_nb.qm src\qt\locale\bitcoin_nl.qm src\qt\locale\bitcoin_ru.qm src\qt\locale\bitcoin_zh_TW.qm
Could Not Find X:\CPP\Applications\SkyCoin\version 0.02 complete try the qt creator with the pro file\skycoin-qt-build-desktop-Qt_4_7_4_for_Desktop_-_MinGW_4_4__Qt_SDK__Debug\build\bitcoin-qt_res.o
del build\moc_bitcoingui.cpp build\moc_transactiontablemodel.cpp build\moc_addresstablemodel.cpp build\moc_optionsdialog.cpp build\moc_sendcoinsdialog.cpp build\moc_addressbookpage.cpp build\moc_aboutdialog.cpp build\moc_editaddressdialog.cpp build\moc_bitcoinaddressvalidator.cpp build\moc_clientmodel.cpp build\moc_optionsmodel.cpp build\moc_monitoreddatamapper.cpp build\moc_transactiondesc.cpp build\moc_transactiondescdialog.cpp build\moc_bitcoinamountfield.cpp build\moc_transactionfilterproxy.cpp build\moc_transactionview.cpp build\moc_walletmodel.cpp build\moc_overviewpage.cpp build\moc_csvmodelwriter.cpp build\moc_sendcoinsentry.cpp build\moc_qvalidatedlineedit.cpp build\moc_qvaluecombobox.cpp build\moc_askpassphrasedialog.cpp build\moc_notificator.cpp
del release\qrc_bitcoin.cpp
del build\optionsdialog.moc build\overviewpage.moc
Could Not Find X:\CPP\Applications\SkyCoin\version 0.02 complete try the qt creator with the pro file\skycoin-qt-build-desktop-Qt_4_7_4_for_Desktop_-_MinGW_4_4__Qt_SDK__Debug\src\qt\locale\bitcoin_da.qm
Could Not Find X:\CPP\Applications\SkyCoin\version 0.02 complete try the qt creator with the pro file\skycoin-qt-build-desktop-Qt_4_7_4_for_Desktop_-_MinGW_4_4__Qt_SDK__Debug\build\moc_bitcoingui.cpp
Could Not Find X:\CPP\Applications\SkyCoin\version 0.02 complete try the qt creator with the pro file\skycoin-qt-build-desktop-Qt_4_7_4_for_Desktop_-_MinGW_4_4__Qt_SDK__Debug\release\qrc_bitcoin.cpp
del build\ui_sendcoinsdialog.h build\ui_addressbookpage.h build\ui_aboutdialog.h build\ui_editaddressdialog.h build\ui_transactiondescdialog.h build\ui_overviewpage.h build\ui_sendcoinsentry.h build\ui_askpassphrasedialog.h
del build\bitcoin.o build\bitcoingui.o build\transactiontablemodel.o build\addresstablemodel.o build\optionsdialog.o build\sendcoinsdialog.o build\addressbookpage.o build\aboutdialog.o build\editaddressdialog.o build\bitcoinaddressvalidator.o build\util.o build\script.o build\main.o build\init.o build\net.o build\irc.o build\db.o build\json_spirit_writer.o build\json_spirit_value.o build\json_spirit_reader.o build\clientmodel.o build\guiutil.o build\transactionrecord.o build\optionsmodel.o build\monitoreddatamapper.o build\transactiondesc.o build\transactiondescdialog.o build\bitcoinstrings.o build\bitcoinamountfield.o build\wallet.o build\keystore.o build\transactionfilterproxy.o build\transactionview.o build\walletmodel.o build\bitcoinrpc.o build\overviewpage.o build\csvmodelwriter.o build\crypter.o build\sendcoinsentry.o build\qvalidatedlineedit.o build\bitcoinunits.o build\qvaluecombobox.o build\askpassphrasedialog.o build\protocol.o build\notificator.o build\moc_bitcoingui.o build\moc_transactiontablemodel.o build\moc_addresstablemodel.o build\moc_optionsdialog.o build\moc_sendcoinsdialog.o build\moc_addressbookpage.o build\moc_aboutdialog.o build\moc_editaddressdialog.o build\moc_bitcoinaddressvalidator.o build\moc_clientmodel.o build\moc_optionsmodel.o build\moc_monitoreddatamapper.o build\moc_transactiondesc.o build\moc_transactiondescdialog.o build\moc_bitcoinamountfield.o build\moc_transactionfilterproxy.o build\moc_transactionview.o build\moc_walletmodel.o build\moc_overviewpage.o build\moc_csvmodelwriter.o build\moc_sendcoinsentry.o build\moc_qvalidatedlineedit.o build\moc_qvaluecombobox.o build\moc_askpassphrasedialog.o build\moc_notificator.o build\qrc_bitcoin.o
del build\bitcoin-qt_res.o
Could Not Find X:\CPP\Applications\SkyCoin\version 0.02 complete try the qt creator with the pro file\skycoin-qt-build-desktop-Qt_4_7_4_for_Desktop_-_MinGW_4_4__Qt_SDK__Debug\build\optionsdialog.moc
Could Not Find X:\CPP\Applications\SkyCoin\version 0.02 complete try the qt creator with the pro file\skycoin-qt-build-desktop-Qt_4_7_4_for_Desktop_-_MinGW_4_4__Qt_SDK__Debug\build\ui_sendcoinsdialog.h
Could Not Find X:\CPP\Applications\SkyCoin\version 0.02 complete try the qt creator with the pro file\skycoin-qt-build-desktop-Qt_4_7_4_for_Desktop_-_MinGW_4_4__Qt_SDK__Debug\build\bitcoin.o
mingw32-make[1]: Leaving directory `X:/CPP/Applications/SkyCoin/version 0.02 complete try the qt creator with the pro file/skycoin-qt-build-desktop-Qt_4_7_4_for_Desktop_-_MinGW_4_4__Qt_SDK__Debug'
Could Not Find X:\CPP\Applications\SkyCoin\version 0.02 complete try the qt creator with the pro file\skycoin-qt-build-desktop-Qt_4_7_4_for_Desktop_-_MinGW_4_4__Qt_SDK__Debug\build\bitcoin-qt_res.o
The process "C:\Tools\QtSDK\mingw\bin\mingw32-make.exe" exited normally.
Configuration unchanged, skipping qmake step.
Starting: "C:\Tools\QtSDK\mingw\bin\mingw32-make.exe"
C:/Tools/QtSDK/mingw/bin/mingw32-make -f Makefile.Debug
mingw32-make[1]: Entering directory `X:/CPP/Applications/SkyCoin/version 0.02 complete try the qt creator with the pro file/skycoin-qt-build-desktop-Qt_4_7_4_for_Desktop_-_MinGW_4_4__Qt_SDK__Debug'
c:\Tools\QtSDK\Desktop\Qt\4.7.4\mingw\bin\lrelease.exe ..\src\src\qt\locale\bitcoin_da.ts
Updating '..\src\src\qt\locale\bitcoin_da.qm'...
Generated 342 translation(s) (342 finished and 0 unfinished)
Ignored 84 untranslated source text(s)
c:\Tools\QtSDK\Desktop\Qt\4.7.4\mingw\bin\lrelease.exe ..\src\src\qt\locale\bitcoin_de.ts
Updating '..\src\src\qt\locale\bitcoin_de.qm'...
Generated 343 translation(s) (343 finished and 0 unfinished)
Ignored 83 untranslated source text(s)
c:\Tools\QtSDK\Desktop\Qt\4.7.4\mingw\bin\lrelease.exe ..\src\src\qt\locale\bitcoin_en.ts
Updating '..\src\src\qt\locale\bitcoin_en.qm'...
Generated 7 translation(s) (0 finished and 7 unfinished)
Ignored 419 untranslated source text(s)
c:\Tools\QtSDK\Desktop\Qt\4.7.4\mingw\bin\lrelease.exe ..\src\src\qt\locale\bitcoin_es.ts
Updating '..\src\src\qt\locale\bitcoin_es.qm'...
Generated 423 translation(s) (423 finished and 0 unfinished)
Ignored 3 untranslated source text(s)
c:\Tools\QtSDK\Desktop\Qt\4.7.4\mingw\bin\lrelease.exe ..\src\src\qt\locale\bitcoin_es_CL.ts
Updating '..\src\src\qt\locale\bitcoin_es_CL.qm'...
Generated 423 translation(s) (423 finished and 0 unfinished)
Ignored 3 untranslated source text(s)
c:\Tools\QtSDK\Desktop\Qt\4.7.4\mingw\bin\lrelease.exe ..\src\src\qt\locale\bitcoin_nb.ts
Updating '..\src\src\qt\locale\bitcoin_nb.qm'...
Generated 423 translation(s) (423 finished and 0 unfinished)
Ignored 3 untranslated source text(s)
c:\Tools\QtSDK\Desktop\Qt\4.7.4\mingw\bin\lrelease.exe ..\src\src\qt\locale\bitcoin_nl.ts
Updating '..\src\src\qt\locale\bitcoin_nl.qm'...
Generated 423 translation(s) (423 finished and 0 unfinished)
Ignored 3 untranslated source text(s)
c:\Tools\QtSDK\Desktop\Qt\4.7.4\mingw\bin\lrelease.exe ..\src\src\qt\locale\bitcoin_ru.ts
Updating '..\src\src\qt\locale\bitcoin_ru.qm'...
Generated 376 translation(s) (376 finished and 0 unfinished)
Ignored 50 untranslated source text(s)
c:\Tools\QtSDK\Desktop\Qt\4.7.4\mingw\bin\lrelease.exe ..\src\src\qt\locale\bitcoin_zh_TW.ts
Updating '..\src\src\qt\locale\bitcoin_zh_TW.qm'...
Generated 423 translation(s) (423 finished and 0 unfinished)
Ignored 3 untranslated source text(s)
c:\Tools\QtSDK\Desktop\Qt\4.7.4\mingw\bin\uic.exe ..\src\src\qt\forms\sendcoinsdialog.ui -o build\ui_sendcoinsdialog.h
c:\Tools\QtSDK\Desktop\Qt\4.7.4\mingw\bin\uic.exe ..\src\src\qt\forms\addressbookpage.ui -o build\ui_addressbookpage.h
c:\Tools\QtSDK\Desktop\Qt\4.7.4\mingw\bin\uic.exe ..\src\src\qt\forms\aboutdialog.ui -o build\ui_aboutdialog.h
c:\Tools\QtSDK\Desktop\Qt\4.7.4\mingw\bin\uic.exe ..\src\src\qt\forms\editaddressdialog.ui -o build\ui_editaddressdialog.h
c:\Tools\QtSDK\Desktop\Qt\4.7.4\mingw\bin\uic.exe ..\src\src\qt\forms\transactiondescdialog.ui -o build\ui_transactiondescdialog.h
c:\Tools\QtSDK\Desktop\Qt\4.7.4\mingw\bin\uic.exe ..\src\src\qt\forms\overviewpage.ui -o build\ui_overviewpage.h
c:\Tools\QtSDK\Desktop\Qt\4.7.4\mingw\bin\uic.exe ..\src\src\qt\forms\sendcoinsentry.ui -o build\ui_sendcoinsentry.h
c:\Tools\QtSDK\Desktop\Qt\4.7.4\mingw\bin\uic.exe ..\src\src\qt\forms\askpassphrasedialog.ui -o build\ui_askpassphrasedialog.h
g++ -c -g -frtti -fexceptions -mthreads -fdiagnostics-show-option -Wall -Wno-strict-aliasing -Wno-invalid-offsetof -Wno-unused-variable -Wno-unused-parameter -Wno-sign-compare -Wno-char-subscripts -Wno-unused-value -Wno-sequence-point -Wno-parentheses -Wno-unknown-pragmas -Wno-switch -DUNICODE -DQT_LARGEFILE_SUPPORT -DQT_GUI -DBOOST_THREAD_USE_LIB -DUSE_UPNP=1 -DSTATICLIB -DWIN32 -DQT_DLL -DQT_GUI_LIB -DQT_CORE_LIB -DQT_HAVE_MMX -DQT_HAVE_3DNOW -DQT_HAVE_SSE -DQT_HAVE_MMXEXT -DQT_HAVE_SSE2 -DQT_THREAD_SUPPORT -DQT_NEEDS_QMAIN -I"c:\Tools\QtSDK\Desktop\Qt\4.7.4\mingw\include\QtCore" -I"c:\Tools\QtSDK\Desktop\Qt\4.7.4\mingw\include\QtGui" -I"c:\Tools\QtSDK\Desktop\Qt\4.7.4\mingw\include" -I"..\src\src" -I"..\src\src\json" -I"..\src\src\qt" -I"..\..\..\..\Libraries\Boost\version 1.48.0" -I"..\..\..\..\Libraries\Berkeley DB\version 4.8.30.NC\build_windows" -I"..\..\..\..\Libraries\OpenSSL\version 1.0.0e\include" -I"c:\Tools\QtSDK\Desktop\Qt\4.7.4\mingw\include\ActiveQt" -I"build" -I"build" -I"." -I"c:\Tools\QtSDK\Desktop\Qt\4.7.4\mingw\mkspecs\win32-g++" -o build\bitcoin.o ..\src\src\qt\bitcoin.cpp
In file included from ..\..\..\..\Libraries\Berkeley DB\version 4.8.30.NC\build_windows/db_cxx.h:65,
from ..\src\src/headers.h:42,
from ..\src\src\qt\bitcoin.cpp:9:
..\..\..\..\Libraries\Berkeley DB\version 4.8.30.NC\build_windows/db.h:135: error: conflicting declaration 'typedef int32_t ssize_t'
c:\tools\qtsdk\mingw\bin\../lib/gcc/mingw32/4.4.0/../../../../include/sys/types.h:104: error: 'ssize_t' has a previous declaration as 'typedef _ssize_t ssize_t'
mingw32-make[1]: Leaving directory `X:/CPP/Applications/SkyCoin/version 0.02 complete try the qt creator with the pro file/skycoin-qt-build-desktop-Qt_4_7_4_for_Desktop_-_MinGW_4_4__Qt_SDK__Debug'
mingw32-make[1]: *** [build/bitcoin.o] Error 1
mingw32-make: *** [debug] Error 2
The process "C:\Tools\QtSDK\mingw\bin\mingw32-make.exe" exited with code 2.
Error while building project skycoin-qt (target: Desktop)
When executing build step 'Make'
Bye, Skybuck. |
|
|
|
"Skycoin Development Donations" at bitcoin address:
12PWQyxrRdjQHV29Ai5fiALP25Q3mT2kFv
Surely you meant to say thats your Skycoin/buck address  Yes ? That's how I labelled it in the bitcoin client !   Oh now I get it ok. So you want SkyAddresses too ? (Or Skycoin Addresses ! ) |
|
|
|
This sounds completely unnecessary. There are far too many useful projects being developed to put time into one that is literally only different in name. At least you aren't making a fork of the chain, but I'm actually not sure if that makes your client any better.
Perhaps I add some nice features to it in the future |
|
|
|
3. Instead of storing the transactions, the balances are stored, which could cut back on data. This would require quite a rework on the entire bitcoin network. Not really, the balance chain would be something extra. It could even start locally for each client without any additional protocol, a balance chain protocol could be added later on. Right now it is based on transactions not just for the sake of it, but for flexibility which is achieved with scripts. Basically a transaction can have many different inputs and many different outputs, and many different conditions that will have to be med to claim the outputs. Just throwing this all away and simply storing balances of each address would not be compatible with this and would mean we would have to rework the whole concept.
Cool idea though.
I don't see how it would be incompatible since bit coin addresses start with a balance at 0. Instead now bit coin addresses can be at an arbitrary value, which is validated by the balance chain, and thus inputs and outputs could be resolved up to that balance value ?!? So instead of solving it to 0, it is solved to balance value. If you believe otherwise, then please try to explain why this would not work, or where problems/incompatibilities would be. |
|
|
|
|
The 0.00000001 I sent myself, still has not arrived, any idea why ?
|
|
|
|
|
I get it:
Bright, Thoughtful Currency,
aBsolute sTraight aCtion,
saBine enTrepreneurs baCk
staBle basTion stoCk
|
|
|
|
I completely do not understand your proposal it's enormously complex and relies on additional communication providing data which might or might not be available. But reading your ideas I have my own idea: (Editi/Addition:Ok, now I understand your proposal better, I didn't know what a ledger is lol I think our ideas are similiar, except my idea was to create a new protocol to exchange the ledger hashes, apperently your idea is to embed those into the block chains, so no new protocol would be necessary, However a drawback of your idea would be that only miners get to verify the ledger/balance sheet, an obvious flaw I think It needs to be seperated so everybody can have a vote on it ! Then again, blocks are the way the network protocol and verification works, this could mean miners are now in control and decide what transactions are valid and which are not, those it seems bitcoin is coming down crashing and burning it's no longer p2p, it's no longer everybody in control, only the miners are now in control, probably a very dangerous situation at least non-miners can still verify, but rejecting will be useless it seems, since they can never win). How about this instead: 1. Instead of storing all transactions which ever occured, a point in historic time is chosen, where the software makes up the balances of all bitcoin addresses. 2. Bitcoin addresses which have turned into zero balances are thrown away. 3. Instead of storing the transactions, the balances are stored, which could cut back on data. What kind of problems could this solution face and what could be the additional solutions: 1. Somebody could change it's own balance in it's own data, to give himself a million dollars. This would then conflict with the datasets of others. An idea could be to calculate a hash over all bit coin address balances. This hash is then broadcasted throughout the system. The number of confirmations is tracked. If the majority agrees that the hash is indeed correct it is accepted into a "balance chain". To make it a little bit more difficult to fake this balance chain, the hash could follow the principle of "difficulty", except since there is no rush, the difficulty could be set 100x times the current difficulty. (Perhaps the difficult setting for the balance should match the number of "transaction/blocks collapses" * "current difficulty". In other words, blocks are calculated every 10 minutes, the balance block is calculated every 1000 blocks. So the difficulty for the balance chain is 1000x the block difficulty, which should keep both in sync). Seems simply enough idea. In principle there is probably no difference between "storing transactions" or "storing the sum of all those transactions" ?!?!? Except that those transactions are "hashed into a block chain". Well the same can be done with a "balance chain". Perhaps it should also become a "racing balance chain" where the longest balance chain wins. The difference is however: the balance chain is much harder to calculate. Also the balance chain lags behind the transaction chain, by for example 1000 or 2000 blocks. So the transaction chain gets a chance to stabilize, so the balance chain can work on stabilized transaction/block data. |
|
|
|
Seeing "copy wallet" in the source code is laughable However there is some merit in this idea: 1. I generate bit coin addresses on my computer, on my "secure" wallet. 2. I then transfer my public bit coin addresses into a file. 3. I then upload this file to some webserver. 4. Your PHP script then simply selects a public bit coin address at random. That way it becomes harder to identify me, but there is also a problem. I cannot identify the user which sent me something if the bit coin addresses are reused. So instead: 1. Each public bit coin address should only be used once. 2. The php script should maintain which bit coin addresses, where used, this can become difficult since it's not known if the transaction occured. 3. The user has to get a warning if addresses used up. So there are still some technical hurdles with this concept/idea. |
|
|
|
Lol, I just realized something, maybe it's the coin "in skycoin" which still sounds silly. Maybe I should just call it Skybuck ! LOL. I always wanted something like this ! LOL. Maybe I should therefore try both and see which one catches on ! LOL. If I do decide to try skybuck as well then it will be here: www.skybuck.orgMaybe even skybuck sounds silly, maybe it should have been skydollar or skydollars. But those domain names already taken, so skybuck will have to do. But Skybuck it's my fricking nickname lol, I would like to keep it like that lol. So I will stick to Skycoin ! hihihihi. But "Hey you want some skybucks" does sound kinda nice. Or he... "pay me some skybucks and we got a deal !" Hmm Maybe buck sounds to american... maybe foreigners who might be anti american might not like that... though dollars could be populair outside of usa too. However when the dollar also known as a buck crashes, then I don't want it to infect me So maybe it's better not to associate it with a buck |
|
|
|
I can't help it but I keep thinking this suits it pretty well in the minds of doubters: Bad Teasing Coin Therefore I am gonna do www.skycoins.comMaybe that sounds better |
|
|
|
Hello, Bitcoins sounds kinda bad, like badcoins. Therefore I think it's a much better idea to make it sounds more friendly, and the sky is always friendly. Therefore I am going to make a bitcoin compatible client. It will be called Skycoin. And it will soon be hosted here: www.skycoins.com(Unfortunately later I discovered skycoin.com was already taken but wtf, I'll just go through with it anyway, since I already payed for the domain lol) At first it will be exactly the same as bitcoin client, but then over time improvements will be added which I would like to see myself, like more insight and such. Like a somewhat more intelligent client. If you think this is a good idea and you want to help out and perhaps even get payed for it on the long run then here is what you can already do: 1. Design a nice Skycoin logo. For example a golden coin with an S inside of it, or perhaps a blue coin with a golden S inside of it ! 2. Make a nice little website for Skycoin, with nice graphics. 3. If necessary I could also host a webforum for it, and you could be a webforum admin to keep things in order. 4. Make a donation to: "Skycoin Development Donations" at bitcoin address: 12PWQyxrRdjQHV29Ai5fiALP25Q3mT2kFv Then I can use these funds to pay people to help extend it. Bye, Skybuck. |
|
|
|
Hello, What are all these 0.1 btc trades on the bitcoin monitor, it seems to be happening since a few days but I could be wrong: http://www.bitcoinmonitor.com/I think it's probably somebody trying to generate a lot of transaction data, so all our harddisk become full real fast, what do you think ?! =D (Perhaps like a stress test for the bitcoin system ?!?) Or it's probably from bitcoin miners/pools ! Deepbit has the minimum payment ammount set to 0.1. So it's probably deepbit sending out payments to miners ! Too funny ! =D These seem to be trades though (=red=bitcoins to dollars)) ! not transactions (=blue=bitcoin to bitcount) ! (Perhaps there should also be green ? dollars to bitcoin ?) So it seems to me, all these bitcoin miners are quickly "cashing out" since the bitcoin value in dollars is dropping all the time ! Bye, Skybuck. |
|
|
|
Let's see what the consequence would be of a storage fee... For example: 0.00000001 bts per byte. This would mean in the scenerio of a million dollars per bitcoin, each byte would be worth 1 dollar cent. A terrabyte would then be worth: 1.099.511.627.776 dollar cents. Which would be pretty much insane. Even if this is divided by a million dollars, so it goes back to 1 dollar equaling 1 bit coin it would be: 1.099.511,627.776 dollar cents. Which would still be very expensive for just 1 terrabyte. Everybody storing bitcoin data would then become a milionair lol ! So I think from this very easy thought exercise it's already clear that only 8 digits behind the comma is not sufficient at all. This would need to be double to 16 at least. Even 16 would probably not be enough real soon, as the data skyrockets passed 16 terrabyte. Binary fractions work like: 1/2 1/4 1/8 = roughly 0.1 1/16 1/32 1/64 = roughly 0.01 1/128 1/256 1/512 1/1024 = roughly 0.001 1/2048 1/4096 1/8192 1/16K = roughly 0.0001 and so forth... what we are looking for is something like: 0.01234567890123456789012345678901234567890123456789 ^ This should be roughly enough for a while, just a wild guess. That's a BIGGGG binary fraction number let's see how big: log10(101234567890123456789012345678901234567890123456789)/log(2) = 102 bits for fractions. 64 bit doubles have about 48 bits or 52 or 56 bits of fractional precision or something, so not even close enough for this number so it can last a while. So it seems pretty clear that for the future computer systems will require 128 bit floating point numbers, maybe even 256 bit floating point numbers. The more bits the better ! |
|
|
|
Ok, I just noticed there is a minimum transaction fee of 0.0005 in the bitcoin 0.5 client. I wanted to send 0.00000001 to myself as a test to see if it really works, and to have fun on the monitor and block explorer or something ! =D So I ended up paying much more to other guys then myself !  =D So my question is basically: Is this minimum transaction fee really required for bitcoin ? or is it possible to send small values without paying transaction fees ? Maybe by using a different client ?!? This might have implications for the future when BitCoins become worth 1.000.000 dollars ! 0.0005 of a million dollars = 500 dollars ! I think 500 dollars is a bit too much to pay for a transaction fee ! Also the ammount I ended up sending to myself would have been only: 0.00000001 of a million dollars which would be: 0.01 dollar ( 1 dollar cent ) ! So I just ended up paying 500 dollars to transfer 0.01 dollar ( 1 dollar cent ) ! Well in the future with the current client system I can forget about micro payments and transactions ! At least with bitcoin 0.5 ?! It will be interesting to see how people react to such ridicilous high fees ! Possible conclusion: Maybe micro-transactions are a pipe-dream ! Because the ammount of harddisk space to store the transaction costs more than the transaction is worth itself, except for the fee, but nobody is going to pay a high fee like that. And there is also an unfairness in this system, only the miners get a share of the fee. All other clients which store the data on their harddisks get nothing ! So perhaps there should be a "storage fee" as well. Which would then go to all clients storing data on their drives ! Except there could be a problem with it, because this would cause even more micro-transactions, unless there is some easy way to make "mass-micro-payments-to-select-groups-of-people/acounts". Perhaps some kind of "bitset transaction", where each bit represents an account. Perhaps this could be a bit pattern in a tree, with the leaves of the tree being active clients at the moment of transaction and/or storage. Or perhaps each client which passes on the transaction to somebody else, can remove the previous client from the transaction, and add himself to the transaction, but then there is a problem of different storage/archives/history, but perhaps there could be a way to allow that, or perhaps not. As long as perhaps something remains the same or so, perhaps a hash collision for a simple hash algorithm, which the storage provided must use. Then again if it's too easy perhaps others can then go back in time and fake it too easy, but then again maybe not because of the block. Well whatever. I think it's clear that there must also be some "storage fee and incentive" otherwise this gonna suck long term, with crazy micro transactions, which actually cost more to store then they are worth, which would be weird, and be a burden on the storage providers. Perhaps storage providers should "register" themselfes among a p2p network, to get an easy/small bit pattern assigned to them, which can then be used somehow or so. This leaves bandwidth fees, which might also be considered... perhaps I should read that document of microsoft a bit closer, I already scanned it a little bit, but it does sound kinda complex. Oh well... I look forward to seeing my micro transaction arrive ! =D Also the bitcoin monitor does show that it's still somehow possible to do transactions without fees ?!? Or perhaps I miss-understood ! |
|
|
|
|
Bypass Taxes Concurrently
Bypass Taxes Collectively
Bypass Taxes Commonly
Bypass Taxes Completely
|
|
|
|
|
Buy The Cash
Banks Till Collapse
|
|
|
|
Perhaps I miss-understand the roll of the hashes and the merkle hash tree. This article seems to explain it a bit more: http://sakabatou.dyndns.org/b2evolution/index.php/2011/09/04/how-does-bitcoin-work-technicalApperently the merkle hash tree is used to allow, multiple chains to exist. Once the longer chain is discovered after 100 blocks it becomes the main chain. The other leaves/trees are collapse and re-fed into the system/chain/merkle hash to be tried and reincluded into the system. So perhaps the blockchain itself is never pruned ?!? The tail is never cut off !? The blockchain must always keep existing ?!? This then raises the question: What if the blockchain becomes to large for average computers to store ?!?!?!? Does this mean that if bitcoin grows faster then harddisk space that bitcoin will more or less be doomed ?! At least for average people ?!? Hmmm... Maybe some compression can help for a while... I shall have to re-examine how it all works and what's possible for attack vectors |
|
|
|
|
Bust Then Complain.
Boom Then Complain.
Burst Then Complain.
Broken Then Complain.
Bust Then Cashout.
Bust Then Cu.
Booming Then Crush.
|
|
|
|
When you spend coins, you tell the network: I take the coins from this transaction and that transaction as inputs, and send them to this address and that address as outputs. You never actually store any coins, you just know which transactions went to your address, and which of those have been "spent", i.e., sent to a different address.
If the blockchain is collapsed or whatever, only the transactions that have been spent would be removed. That way you could still scan the blockchain, and find out how much money you have, by adding all transactions that have not yet been spent.
If there was an attacker claiming "Look! I have this trail of (fake) transactions, and they add up to this hash!" then they would still need to add up to the transactions to your address which you haven't spent yet. This means the attacker doesn't actually achieve anything with his 'attack'. That is beside the point that finding a hash collision really is impossible for the coming few decades.
What matters is what is stored. The transactions as far as I know are stored on disk ? The transactions are the archive which could be used to makes sense out of things. You seem to imply that there is a difference between "spending" and "receiving" ? Does this mean there is a difference between "spent" and "receive" transactions ? What does this mean for a potential collapse/cut of of the trail ? Does this mean all "receive transactions" are kept and the "spent transactions" can be thrown away ? If so then suddenly you would become rich because it would seem you didn't spent anything ? So that doesn't make sense. Another conclusion could be possible as well: If the fake blockchain does not add up to your account balance, then your account balance is fraud ! In another words if suddenly the fake blockchain would be acceptable by a majority for some strange reasons, for example some people got rich and don't mind getting rich, and some people lost a lot, then oops. If you would be the person suddenly losing a lot, and you complained the guys who got rich would say well ofcourse he's complaining, he's poor and a fraud ! |
|
|
|
|
Show Posts
