David, when you've talked about "licensing halo" for another altcoin, do you mean that the altcoin would get its own decentralized market with double deposit escrow capability from you, or the existing market would start supporting that altcoin in addition to BTC, BLK, and BAY, or the altcoin would have to create its own market place but could use halo to implement double deposit escrow?
Topic: BitBay OFFICIAL BITBAY Thread Smart Contracts Decentralized Markets Rolling Peg - page 329. (Read 542094 times)
March 26, 2015, 06:57:36 PM
March 26, 2015, 06:57:00 PM
Just a quick question. Does the Bitbay Marketplace wallet/app also stake ? Or do i need to download the wallet-qt for staking ?
Or if it doesnt right now, will it once it is fully released ?
For now the only way to stake is with the QT wallet, but we are looking into implementing it in the client.Or if it doesnt right now, will it once it is fully released ?
Would be nice to have it in the client
Btw that client for the marketplace looks really nice
I hear ya. It's going to happen, eventually.
For now, I'm gonna fire up my old crappy laptop to stake my wallet. That way I can play around with the beta client on my regular PC without missing a beat on the stake reward.
March 26, 2015, 12:31:25 PM
Just a quick question. Does the Bitbay Marketplace wallet/app also stake ? Or do i need to download the wallet-qt for staking ?
Or if it doesnt right now, will it once it is fully released ?
For now the only way to stake is with the QT wallet, but we are looking into implementing it in the client.Or if it doesnt right now, will it once it is fully released ?
Would be nice to have it in the client
Btw that client for the marketplace looks really nice
March 26, 2015, 12:29:31 PM
Just a quick question. Does the Bitbay Marketplace wallet/app also stake ? Or do i need to download the wallet-qt for staking ?
Or if it doesnt right now, will it once it is fully released ?
For now the only way to stake is with the QT wallet, but we are looking into implementing it in the client. Or if it doesnt right now, will it once it is fully released ?
March 26, 2015, 11:22:39 AM
Just a quick question. Does the Bitbay Marketplace wallet/app also stake ? Or do i need to download the wallet-qt for staking ?
Or if it doesnt right now, will it once it is fully released ?
Or if it doesnt right now, will it once it is fully released ?
March 26, 2015, 09:49:22 AM
The BitBay client works fine its only calling the daemons as a subprocess. Bitbayd and Blackcoind. Getting a static build that is good for commercial release.
For example we were told getting a linux build for all versions of linux in one client is not practical because of libraries for certain computers being different. Our windows build works on 100% of the systems currently. The others working on more than 90% (according to reports vs download counter)
For example we were told getting a linux build for all versions of linux in one client is not practical because of libraries for certain computers being different. Our windows build works on 100% of the systems currently. The others working on more than 90% (according to reports vs download counter)
Commercial release ?
Linux versions do not vary by "computer". There are three main versions of Linux and most other distros are versions of those versions. Those are RedHat, Debian, Suse. For instance, anything compiled on Redhat will run on CentOs. The only thing that varies for executables are library linkages, so compiling for any particular distro fixes that. Most all distros you'll ever see are available for free on distrowatch.com. You can just boot them into a VM in virtualbox and do a compile to produce the executables for your code. Easy Peasy. Are you distributing you Linux code as .tgz or native packages?
I take some of that back. Linux does vary by hardware architecture. X86, IBM power Series. You're not going to be running in AIX lpars by any chance, are you?
Also a static build of the client should work on all X86 based distros without a problem.
Not exactly true, lubuntu, mint and other platforms all differ slightly. Depending on the libraries, this may matter and we have seen it make a difference. Shit even windows distros on windows 7 arent the same! Lots of computers are different. If I had a github for people to pull and run the source, then it wouldnt be a problem. For linux its a tarball but we make deb files. I've even noticed a difference on Mac platforms.
Also, there is the simple fact that 32 and 64 bit is different. We only have 64 bit builds for Linux and Mac. 32 bit for Windows. I used to build windows 64 but regressed to 32 so it would always be the same. I was told 64 bit linux wasnt backwards compatible but have not tested that yet since we only have 64 bit build anyways. Not to mention it runs bitmessage, coin daemons and all the qt and crypto python libraries. So there is tons of things to consider when packaging for disto.
I must have still been sleeping. Use Docker and all these problems go away.
Ok I will give that a shot. Thanks.
March 26, 2015, 09:46:24 AM
The BitBay client works fine its only calling the daemons as a subprocess. Bitbayd and Blackcoind. Getting a static build that is good for commercial release.
For example we were told getting a linux build for all versions of linux in one client is not practical because of libraries for certain computers being different. Our windows build works on 100% of the systems currently. The others working on more than 90% (according to reports vs download counter)
For example we were told getting a linux build for all versions of linux in one client is not practical because of libraries for certain computers being different. Our windows build works on 100% of the systems currently. The others working on more than 90% (according to reports vs download counter)
Commercial release ?
Linux versions do not vary by "computer". There are three main versions of Linux and most other distros are versions of those versions. Those are RedHat, Debian, Suse. For instance, anything compiled on Redhat will run on CentOs. The only thing that varies for executables are library linkages, so compiling for any particular distro fixes that. Most all distros you'll ever see are available for free on distrowatch.com. You can just boot them into a VM in virtualbox and do a compile to produce the executables for your code. Easy Peasy. Are you distributing you Linux code as .tgz or native packages?
I take some of that back. Linux does vary by hardware architecture. X86, IBM power Series. You're not going to be running in AIX lpars by any chance, are you?
Also a static build of the client should work on all X86 based distros without a problem.
Not exactly true, lubuntu, mint and other platforms all differ slightly. Depending on the libraries, this may matter and we have seen it make a difference. Shit even windows distros on windows 7 arent the same! Lots of computers are different. If I had a github for people to pull and run the source, then it wouldnt be a problem. For linux its a tarball but we make deb files. I've even noticed a difference on Mac platforms.
Also, there is the simple fact that 32 and 64 bit is different. We only have 64 bit builds for Linux and Mac. 32 bit for Windows. I used to build windows 64 but regressed to 32 so it would always be the same. I was told 64 bit linux wasnt backwards compatible but have not tested that yet since we only have 64 bit build anyways. Not to mention it runs bitmessage, coin daemons and all the qt and crypto python libraries. So there is tons of things to consider when packaging for disto.
I must have still been sleeping. Use Docker and all these problems go away.
March 26, 2015, 09:44:53 AM
Did you install to somewhere where you have no write access? Or are you trying to save keys to certain directories without write access? I saw this issue before with my friends computer. It wasnt allowed to save to certain directories! Go ahead and see where you can write to. Also, make sure it has admin privelages.
Does the client display an error message when it experiences a write error?
Nope, but the write permission error will only happen when trying to make new wallets. If it happened with the core program, it wouldnt load.
Oh! One reason for the error too might be to save to a folder that isnt unicode. For example, you have a non-alphanumeric character in your username like a chinese character. I think its a pyqt thing. Bitmessage had the same bug which is why i simply save their data locally.
Ouch. Nothing pisses me off like programs that fail silently. Many issues are easily overcome if the programmer just gets the error out to the display. Aren't you checking return codes or something?
There are no such things as Unicode folders. NTFS supports unicode. All filenames are saved as unicode. Otherwise things like French and German don't work well. Pyqt seems to handle unicode correctly if you use the calls correctly. bitmessage had programming errors that were fixed with patches. Since NTFS supports Unicode at the file system level, what do you mean by "save their data locally" ? What do unicode usernames have to do with saving files? Or maybe I'm completely missing something here?
Bitmessage did not fix this specific bug. I had to fix it manually. Try running it on a German computer and then get back to me
... Sadly, pyqt doesnt handle it correctly at least natively from version 4. Its on my bug tracker to be fixed but havent had the time to look into that one. What i meant by saving data locally was that i dont save bitmessage data in the default datadir in roaming. Instead, i save to install path. I had to change this manually in their source, its not a big deal. Because on a German or Chinese computer, their username may use foreign characters and those would cause Bitmessage to fail. So no, not every bug is so transparent. Of course, in pyqt my solution will be different however there is two folder issues. One being for foreign characters and another being for windows BS security that doesnt let you write to certain directories unless you run as admin. Oh and i almost forgot. I've got an admin hack but it doesnt work on the subprocesses. To blackcoind needs to be run as admin too on certain computers from the terminal/console. I can just have it called with the asadmin flag. I'm not sure if all systems will allow that though.
March 26, 2015, 09:39:35 AM
The BitBay client works fine its only calling the daemons as a subprocess. Bitbayd and Blackcoind. Getting a static build that is good for commercial release.
For example we were told getting a linux build for all versions of linux in one client is not practical because of libraries for certain computers being different. Our windows build works on 100% of the systems currently. The others working on more than 90% (according to reports vs download counter)
For example we were told getting a linux build for all versions of linux in one client is not practical because of libraries for certain computers being different. Our windows build works on 100% of the systems currently. The others working on more than 90% (according to reports vs download counter)
Commercial release ?
Linux versions do not vary by "computer". There are three main versions of Linux and most other distros are versions of those versions. Those are RedHat, Debian, Suse. For instance, anything compiled on Redhat will run on CentOs. The only thing that varies for executables are library linkages, so compiling for any particular distro fixes that. Most all distros you'll ever see are available for free on distrowatch.com. You can just boot them into a VM in virtualbox and do a compile to produce the executables for your code. Easy Peasy. Are you distributing you Linux code as .tgz or native packages?
I take some of that back. Linux does vary by hardware architecture. X86, IBM power Series. You're not going to be running in AIX lpars by any chance, are you?
Also a static build of the client should work on all X86 based distros without a problem.
Not exactly true, lubuntu, mint and other platforms all differ slightly. Depending on the libraries, this may matter and we have seen it make a difference. Shit even windows distros on windows 7 arent the same! Lots of computers are different. If I had a github for people to pull and run the source, then it wouldnt be a problem. For linux its a tarball but we make deb files. I've even noticed a difference on Mac platforms.
Also, there is the simple fact that 32 and 64 bit is different. We only have 64 bit builds for Linux and Mac. 32 bit for Windows. I used to build windows 64 but regressed to 32 so it would always be the same. I was told 64 bit linux wasnt backwards compatible but have not tested that yet since we only have 64 bit build anyways. Not to mention it runs bitmessage, coin daemons and all the qt and crypto python libraries. So there is tons of things to consider when packaging for disto.
March 26, 2015, 06:13:46 AM
The BitBay client works fine its only calling the daemons as a subprocess. Bitbayd and Blackcoind. Getting a static build that is good for commercial release.
For example we were told getting a linux build for all versions of linux in one client is not practical because of libraries for certain computers being different. Our windows build works on 100% of the systems currently. The others working on more than 90% (according to reports vs download counter)
For example we were told getting a linux build for all versions of linux in one client is not practical because of libraries for certain computers being different. Our windows build works on 100% of the systems currently. The others working on more than 90% (according to reports vs download counter)
Commercial release ?
Linux versions do not vary by "computer". There are three main versions of Linux and most other distros are versions of those versions. Those are RedHat, Debian, Suse. For instance, anything compiled on Redhat will run on CentOs. The only thing that varies for executables are library linkages, so compiling for any particular distro fixes that. Most all distros you'll ever see are available for free on distrowatch.com. You can just boot them into a VM in virtualbox and do a compile to produce the executables for your code. Easy Peasy. Are you distributing you Linux code as .tgz or native packages?
I take some of that back. Linux does vary by hardware architecture. X86, IBM power Series. You're not going to be running in AIX lpars by any chance, are you?
Also a static build of the client should work on all X86 based distros without a problem.
March 26, 2015, 05:42:02 AM
Did you install to somewhere where you have no write access? Or are you trying to save keys to certain directories without write access? I saw this issue before with my friends computer. It wasnt allowed to save to certain directories! Go ahead and see where you can write to. Also, make sure it has admin privelages.
Does the client display an error message when it experiences a write error?
Nope, but the write permission error will only happen when trying to make new wallets. If it happened with the core program, it wouldnt load.
Oh! One reason for the error too might be to save to a folder that isnt unicode. For example, you have a non-alphanumeric character in your username like a chinese character. I think its a pyqt thing. Bitmessage had the same bug which is why i simply save their data locally.
Ouch. Nothing pisses me off like programs that fail silently. Many issues are easily overcome if the programmer just gets the error out to the display. Aren't you checking return codes or something?
There are no such things as Unicode folders. NTFS supports unicode. All filenames are saved as unicode. Otherwise things like French and German don't work well. Pyqt seems to handle unicode correctly if you use the calls correctly. bitmessage had programming errors that were fixed with patches. Since NTFS supports Unicode at the file system level, what do you mean by "save their data locally" ? What do unicode usernames have to do with saving files? Or maybe I'm completely missing something here?
March 26, 2015, 05:37:34 AM
I give this coin my mark of quality and approval it is to be very good for the future of crypto. All the haters are sleeping now maybe even crying they could not derail this beauty aha Congratulations guys!
March 26, 2015, 05:21:38 AM
Looking good David and team, am impressed with this market
Thanks if you want, take one of my contracts or pm me, will walk you through it.
March 26, 2015, 05:09:28 AM
Looking good David and team, am impressed with this market
March 26, 2015, 04:22:22 AM
Did you install to somewhere where you have no write access? Or are you trying to save keys to certain directories without write access? I saw this issue before with my friends computer. It wasnt allowed to save to certain directories! Go ahead and see where you can write to. Also, make sure it has admin privelages.
Does the client display an error message when it experiences a write error?
Nope, but the write permission error will only happen when trying to make new wallets. If it happened with the core program, it wouldnt load.
Oh! One reason for the error too might be to save to a folder that isnt unicode. For example, you have a non-alphanumeric character in your username like a chinese character. I think its a pyqt thing. Bitmessage had the same bug which is why i simply save their data locally.
March 25, 2015, 11:14:27 PM
Did you install to somewhere where you have no write access? Or are you trying to save keys to certain directories without write access? I saw this issue before with my friends computer. It wasnt allowed to save to certain directories! Go ahead and see where you can write to. Also, make sure it has admin privelages.
Does the client display an error message when it experiences a write error?
March 25, 2015, 09:22:36 PM
OK so there was 2 people that didnt see the markets populate. Thats because the default address never loaded. You can solve it by adding it manually to other.dat
If you PM me I can explain how to do it.
Other than that, everything else should be working perfectly.
If you PM me I can explain how to do it.
Other than that, everything else should be working perfectly.
March 25, 2015, 08:18:51 PM
its gone now for me
March 25, 2015, 07:24:13 PM
OK thx for letting me know
March 25, 2015, 07:21:14 PM
I can see your tire pressure gauge.
Screenshot: https://i.imgur.com/w01o9fM.png
Screenshot: https://i.imgur.com/w01o9fM.png
Jump to: