All, I want to state that I support this effort, but will be withdrawing my bid to pursue any part of this bounty due to the progress and funding I am receiving for the development of BitShares.
Topic: Holy Grail BOUNTY - page 9. (Read 36337 times)
Obsi has not been active, but code is on FellowTraveler github, and it's been upgraded constantly.
Better wait for an answer, but if someone is going to countribute, better following this Holy Grail topic and donate through CIYAM.
Better wait for an answer, but if someone is going to countribute, better following this Holy Grail topic and donate through CIYAM.
Are these bounties related in any way?
...
...
I doubt that. It's the same bounty btw. The sponsor or author of OP for the bounty has not been active on this forum in half a year. You better not rely on him to appear and evaluate submitted code.
Are these bounties related in any way?
[BOUNTY] 185+ BTC - Open Transactions Client (for Grandmas)
Open Transactions Client (for Grandmas) - Rugatu
[BOUNTY] 185+ BTC - Open Transactions Client (for Grandmas)
Open Transactions Client (for Grandmas) - Rugatu
OT builds with fPIC turned on.
Is your QT app also building with fPIC turned on?
If not, then I would expect problems to arise at link time. (Which, for dynamic libraries, is at run time.)
Are you noticing, at run time, that a problem occurs in your main app, when you call something from a different shared object?
If so, then it sounds like they aren't compiled with the same options. (Whether 32/64 bit, or fPIC / no-fPIC, etc)
Is your QT app also building with fPIC turned on?
If not, then I would expect problems to arise at link time. (Which, for dynamic libraries, is at run time.)
Are you noticing, at run time, that a problem occurs in your main app, when you call something from a different shared object?
If so, then it sounds like they aren't compiled with the same options. (Whether 32/64 bit, or fPIC / no-fPIC, etc)
Scratch that for now.....
Currently Mt Gox and other exchanges are the only source for price reporting. With a decentralized exchange, how will anybody know how much Bitcoin is worth?
I would assume by tracking and processing the datafeed of the last few transactions that propagated over the network, similar to a blockchain explorer. Only skimmed the thread so far though, so I could be wrong.
Plus, I don't think classic exchanges would disappear. They would keep operating, and arbitrage would guarantee no significant price difference would last long.
Currently Mt Gox and other exchanges are the only source for price reporting. With a decentralized exchange, how will anybody know how much Bitcoin is worth?
I would assume by tracking and processing the datafeed of the last few transactions that propagated over the network, similar to a blockchain explorer. Only skimmed the thread so far though, so I could be wrong.
Currently Mt Gox and other exchanges are the only source for price reporting. With a decentralized exchange, how will anybody know how much Bitcoin is worth?
How do black markets work?
Currently Mt Gox and other exchanges are the only source for price reporting. With a decentralized exchange, how will anybody know how much Bitcoin is worth?
How do black markets work?
Currently Mt Gox and other exchanges are the only source for price reporting. With a decentralized exchange, how will anybody know how much Bitcoin is worth?
edit: Is this the function of the Advanced feature: Markets?
edit: Is this the function of the Advanced feature: Markets?
How would the Integration with legacy banking be done?
Do we initiate the SEPA transaction via some sort of API or do we just tell the user to "go to his banking site and send money to XYZ"?
Do we initiate the SEPA transaction via some sort of API or do we just tell the user to "go to his banking site and send money to XYZ"?
You might want to watch this thread: https://bitcointalksearch.org/topic/tlsnotary-cryptographic-proof-of-fiat-transfer-for-p2p-exchanges-173220
How would the Integration with legacy banking be done?
Do we initiate the SEPA transaction via some sort of API or do we just tell the user to "go to his banking site and send money to XYZ"?
Do we initiate the SEPA transaction via some sort of API or do we just tell the user to "go to his banking site and send money to XYZ"?
Why are you guys donating so much money for this?
60btc for three(?) programmers is actually pretty low payment, even if we manage to finish it in one month (not very likely considering the amount of beta-testing required for such an application) Why are you guys donating so much money for this?
Just an example: https://bitcointalksearch.org/topic/m.2425367
Why are you guys donating so much money for this?
It must be important.
Why are you guys donating so much money for this?
To any QT/C++ devs out there that have a few minutes of their time to help instruct me on how to include shared objects (.so) files along with header files (.h) in the QT Creator .pro setup? if i don't make any sense to you don't reply to this message, Please PM me. I'd be willing to give $50 in BTC value if you can help me get the init command of the OTAPI working on QT Creator. I have experience with including external libraries but mostly major libraries like SSL and the like.
Headers are not included in the project file -- they are included in the CPP files.
(But while building, your compiler will fail to FIND those headers, unless they are on the include path.)
The shared objects (.so files) are the Linux version of DLLs. Since you are installing to $HOME/.local, then you probably just need to make sure that $HOME/.local/lib is on your library path. (It will only find libraries that are on the library path.) I'm willing to bet that this part is already handled by the PKG_CONFIG_PATH which you have already set.
You will also need to make sure that your makefile is linking the appropriate libraries. For example, if you were linking with g++, you would be adding -lotapi to the link step. That's the instruction that tells it to link the otapi library (which it will search for on the library path.) I'm not sure how you instruct a QT project file to link a specific library, but it will be something similar.
Sounds like i did it all correctly. I'll post my .pro file for everyone to review, i even did the -L filepath -lotapi thing as well
To any QT/C++ devs out there that have a few minutes of their time to help instruct me on how to include shared objects (.so) files along with header files (.h) in the QT Creator .pro setup? if i don't make any sense to you don't reply to this message, Please PM me. I'd be willing to give $50 in BTC value if you can help me get the init command of the OTAPI working on QT Creator. I have experience with including external libraries but mostly major libraries like SSL and the like.
Headers are not included in the project file -- they are included in the CPP files.
(But while building, your compiler will fail to FIND those headers, unless they are on the include path.)
The shared objects (.so files) are the Linux version of DLLs. Since you are installing to $HOME/.local, then you probably just need to make sure that $HOME/.local/lib is on your library path. (It will only find libraries that are on the library path.) I'm willing to bet that this part is already handled by the PKG_CONFIG_PATH which you have already set.
You will also need to make sure that your makefile is linking the appropriate libraries. For example, if you were linking with g++, you would be adding -lotapi to the link step. That's the instruction that tells it to link the otapi library (which it will search for on the library path.) I'm not sure how you instruct a QT project file to link a specific library, but it will be something similar.
To any QT/C++ devs out there that have a few minutes of their time to help instruct me on how to include shared objects (.so) files along with header files (.h) in the QT Creator .pro setup? if i don't make any sense to you don't reply to this message, Please PM me. I'd be willing to give $50 in BTC value if you can help me get the init command of the OTAPI working on QT Creator. I have experience with including external libraries but mostly major libraries like SSL and the like.
Jump to: