|
Quadmium
|
 |
December 26, 2014, 08:54:21 PM |
|
Will the source for the wallet be released anytime soon? I can't run the compiled ubuntu binary as it appears to be compiled for 32bit arch. And it does appear a bit fishy that no source is provided, what do you have to hide after all? It's just a bitcoin-qt fork.
The 32-bit binary should run on ubuntu machines, have you used the wrapper? The source was decided to be closed by the community to prevent cheating by adding in proxy options (dev team didn't decide this). We will release it after distribution. |
|
|
|
|
|
fenghush
|
|
December 26, 2014, 08:57:49 PM |
|
Will the source for the wallet be released anytime soon? I can't run the compiled ubuntu binary as it appears to be compiled for 32bit arch. And it does appear a bit fishy that no source is provided, what do you have to hide after all? It's just a bitcoin-qt fork.
The 32-bit binary should run on ubuntu machines, have you used the wrapper? The source was decided to be closed by the community to prevent cheating by adding in proxy options (dev team didn't decide this). I don't have 32bit compat mode enabled on my kernel for security reasons, I'm one of those technically skilled tinfoil hats. Care to elaborate 'cheating by adding in proxy options'? If you mean running more than one wallet per person to cheat the faucet distribution system then it's really contra-productive since I can run as many instances as I want of the wallet via tor and you will never tell the difference so it defeats the whole purpose to hold on to the code. Don't get me wrong I like the idea of this coin and the binaries are probably harmless but in theory they could be running something malicious and without debugging/sniffing packets nobody could tell, with full source code on the other hand such a feat is next to impossible. So in interest of gaining trust with the dev team my opinion is to release the code and figure something better to prevent cheating as it really doesn't stop people to run more than one wallet per IP/machine/whatever. And after all it's almost 2015 who the hell runs 32bit linux boxes? |
|
|
|
c_e_d
Member
 Offline
Activity: 100
Merit: 10
|
|
December 26, 2014, 09:01:47 PM |
|
After reading some of the confusion I will add to the FAQ not to worry about transaction errors.
I am sorry man but I am still confused. will the wallets work for distribution with the other wallet.dat in them or do I need to use a clean wallet for distro? Yea no problem. The wallets will work, but you will see unconfirmed transactions from the old network. These won't affect you during distribution or anything like that. I just added in the exchange form how you can get rid of the old transactions by sending your coins to a new wallet after you receive them from us. TLDR: Wait until you get your coins from exchange and then switch to a new wallet by following steps I just added to the exchange form.Awesome,Thank you  Is there any reasons why not simply use dumpprivkey/importprivkey ? |
|
|
|
|
atchoum6760
Legendary
Offline
Activity: 1904
Merit: 1063
|
|
December 26, 2014, 09:07:02 PM |
|
My wallet don't sync with window 8 i paste .conf but nothing.
|
|
|
|
|
Quadmium
|
|
December 26, 2014, 09:07:32 PM |
|
Will the source for the wallet be released anytime soon? I can't run the compiled ubuntu binary as it appears to be compiled for 32bit arch. And it does appear a bit fishy that no source is provided, what do you have to hide after all? It's just a bitcoin-qt fork.
The 32-bit binary should run on ubuntu machines, have you used the wrapper? The source was decided to be closed by the community to prevent cheating by adding in proxy options (dev team didn't decide this). I don't have 32bit compat mode enabled on my kernel for security reasons, I'm one of those technically skilled tinfoil hats. Care to elaborate 'cheating by adding in proxy options'? If you mean running more than one wallet per person to cheat the faucet distribution system then it's really contra-productive since I can run as many instances as I want of the wallet via tor and you will never tell the difference so it defeats the whole purpose to hold on to the code. Don't get me wrong I like the idea of this coin and the binaries are probably harmless but in theory they could be running something malicious and without debugging/sniffing packets nobody could tell, with full source code on the other hand such a feat is next to impossible. So in interest of gaining trust with the dev team my opinion is to release the code and figure something better to prevent cheating as it really doesn't stop people to run more than one wallet per IP/machine/whatever. And after all it's almost 2015 who the hell runs 32bit linux boxes? 64 bit ubuntu build, care to test? I will discuss release of source code with the team, but I don't believe the community will agree. |
|
|
|
|
|
Quadmium
|
|
December 26, 2014, 09:09:22 PM |
|
After reading some of the confusion I will add to the FAQ not to worry about transaction errors.
I am sorry man but I am still confused. will the wallets work for distribution with the other wallet.dat in them or do I need to use a clean wallet for distro? Yea no problem. The wallets will work, but you will see unconfirmed transactions from the old network. These won't affect you during distribution or anything like that. I just added in the exchange form how you can get rid of the old transactions by sending your coins to a new wallet after you receive them from us. TLDR: Wait until you get your coins from exchange and then switch to a new wallet by following steps I just added to the exchange form.Awesome,Thank you Is there any reasons why not simply use dumpprivkey/importprivkey ? You can use that method once we email you which address the coins were sent to. The wallet.dat way is another option, made for people with less experience with private keys and such. |
|
|
|
|
|
fenghush
|
|
December 26, 2014, 09:10:35 PM |
|
Will the source for the wallet be released anytime soon? I can't run the compiled ubuntu binary as it appears to be compiled for 32bit arch. And it does appear a bit fishy that no source is provided, what do you have to hide after all? It's just a bitcoin-qt fork.
The 32-bit binary should run on ubuntu machines, have you used the wrapper? The source was decided to be closed by the community to prevent cheating by adding in proxy options (dev team didn't decide this). I don't have 32bit compat mode enabled on my kernel for security reasons, I'm one of those technically skilled tinfoil hats. Care to elaborate 'cheating by adding in proxy options'? If you mean running more than one wallet per person to cheat the faucet distribution system then it's really contra-productive since I can run as many instances as I want of the wallet via tor and you will never tell the difference so it defeats the whole purpose to hold on to the code. Don't get me wrong I like the idea of this coin and the binaries are probably harmless but in theory they could be running something malicious and without debugging/sniffing packets nobody could tell, with full source code on the other hand such a feat is next to impossible. So in interest of gaining trust with the dev team my opinion is to release the code and figure something better to prevent cheating as it really doesn't stop people to run more than one wallet per IP/machine/whatever. And after all it's almost 2015 who the hell runs 32bit linux boxes? 64 bit ubuntu build, care to test? I will discuss release of source code with the team, but I don't believe the community will agree. Will do, thank you very much. If I can demonstrate that I can run more than one wallet via different proxies the community would have to agree as their reason for keeping the source code private is without merit. |
|
|
|
|
Quadmium
|
|
December 26, 2014, 09:11:42 PM |
|
My wallet don't sync with window 8 i paste .conf but nothing.
If you head to the debug options under help, what block count do you see? The wallets will be out of sync until the faucet payments begin. We can help you in IRC if you wish. |
|
|
|
|
|
Quadmium
|
|
December 26, 2014, 09:12:50 PM |
|
...
Will do, thank you very much. If I can demonstrate that I can run more than one wallet via different proxies the community would have to agree as their reason for keeping the source code private is without merit.
Yep, we cannot decide what the community wishes to do. This was decided via a vote, as we intend this coin to be run by the community. Best of luck . |
|
|
|
|
atchoum6760
Legendary
Offline
Activity: 1904
Merit: 1063
|
|
December 26, 2014, 09:20:09 PM
Last edit: December 26, 2014, 09:45:03 PM by atchoum6760 |
|
My wallet don't sync with window 8 i paste .conf but nothing.
If you head to the debug options under help, what block count do you see? The wallets will be out of sync until the faucet payments begin. We can help you in IRC if you wish. Now it's sync thx for your help quadmium |
|
|
|
|
fenghush
|
|
December 26, 2014, 09:27:10 PM |
|
...
Will do, thank you very much. If I can demonstrate that I can run more than one wallet via different proxies the community would have to agree as their reason for keeping the source code private is without merit.
Yep, we cannot decide what the community wishes to do. This was decided via a vote, as we intend this coin to be run by the community. Best of luck . I have slightly newer version of libboost. The binary was compiled against 1.54 but I have 1.55, nothing that a bit of symlinking wont fix but I do get these weird X-system errors on console I when I run the client (see bellow) I believe they're just cosmetics and it appears the wallet is working fine. X Error: BadPixmap (invalid Pixmap parameter) 4
Major opcode: 56 (X_ChangeGC)
Resource id: 0x0
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
Major opcode: 62 (X_CopyArea)
Resource id: 0x0
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
Major opcode: 55 (X_CreateGC)
Resource id: 0x0
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
Major opcode: 70 (X_PolyFillRectangle)
Resource id: 0x0
X Error: BadGC (invalid GC parameter) 13
Major opcode: 59 (X_SetClipRectangles)
Resource id: 0x0
X Error: BadGC (invalid GC parameter) 13
Major opcode: 56 (X_ChangeGC)
Resource id: 0x0
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
Major opcode: 70 (X_PolyFillRectangle)
Resource id: 0x0
X Error: BadGC (invalid GC parameter) 13
Major opcode: 60 (X_FreeGC)
Resource id: 0x0
X Error: BadMatch (invalid parameter attributes) 8
Major opcode: 62 (X_CopyArea)
Resource id: 0x740000f
X Error: BadPixmap (invalid Pixmap parameter) 4
Major opcode: 56 (X_ChangeGC)
Resource id: 0x0
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
Major opcode: 62 (X_CopyArea)
Resource id: 0x0
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
Major opcode: 55 (X_CreateGC)
Resource id: 0x0
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
Major opcode: 70 (X_PolyFillRectangle)
Resource id: 0x0
X Error: BadGC (invalid GC parameter) 13
Major opcode: 59 (X_SetClipRectangles)
Resource id: 0x0
X Error: BadGC (invalid GC parameter) 13
Major opcode: 56 (X_ChangeGC)
Resource id: 0x0
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
Major opcode: 70 (X_PolyFillRectangle)
Resource id: 0x0
X Error: BadGC (invalid GC parameter) 13
Major opcode: 60 (X_FreeGC)
Resource id: 0x0
X Error: BadMatch (invalid parameter attributes) 8
Major opcode: 62 (X_CopyArea)
Resource id: 0x740000f
X Error: BadPixmap (invalid Pixmap parameter) 4
Major opcode: 56 (X_ChangeGC)
Resource id: 0x0
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
Major opcode: 62 (X_CopyArea)
Resource id: 0x0
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
Major opcode: 55 (X_CreateGC)
Resource id: 0x0
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
Major opcode: 70 (X_PolyFillRectangle)
Resource id: 0x0
X Error: BadGC (invalid GC parameter) 13
Major opcode: 59 (X_SetClipRectangles)
Resource id: 0x0
X Error: BadGC (invalid GC parameter) 13
Major opcode: 56 (X_ChangeGC)
Resource id: 0x0
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
Major opcode: 70 (X_PolyFillRectangle)
Resource id: 0x0
X Error: BadGC (invalid GC parameter) 13
Major opcode: 60 (X_FreeGC)
Resource id: 0x0
X Error: BadMatch (invalid parameter attributes) 8
Major opcode: 62 (X_CopyArea)
Resource id: 0x740000f
|
|
|
|
FindCoin (OP)
Newbie
Offline
Activity: 10
Merit: 0
|
|
December 26, 2014, 09:28:57 PM |
|
...
Will do, thank you very much. If I can demonstrate that I can run more than one wallet via different proxies the community would have to agree as their reason for keeping the source code private is without merit.
Yep, we cannot decide what the community wishes to do. This was decided via a vote, as we intend this coin to be run by the community. Best of luck . I have slightly newer version of libboost. The binary was compiled against 1.54 but I have 1.55, nothing that a bit of symlinking wont fix but I do get these weird X-system errors on console I when I run the client (see bellow) I believe they're just cosmetics and it appears the wallet is working fine. X Error: BadPixmap (invalid Pixmap parameter) 4
Major opcode: 56 (X_ChangeGC)
Resource id: 0x0
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
Major opcode: 62 (X_CopyArea)
Resource id: 0x0
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
Major opcode: 55 (X_CreateGC)
Resource id: 0x0
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
Major opcode: 70 (X_PolyFillRectangle)
Resource id: 0x0
X Error: BadGC (invalid GC parameter) 13
Major opcode: 59 (X_SetClipRectangles)
Resource id: 0x0
X Error: BadGC (invalid GC parameter) 13
Major opcode: 56 (X_ChangeGC)
Resource id: 0x0
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
Major opcode: 70 (X_PolyFillRectangle)
Resource id: 0x0
X Error: BadGC (invalid GC parameter) 13
Major opcode: 60 (X_FreeGC)
Resource id: 0x0
X Error: BadMatch (invalid parameter attributes) 8
Major opcode: 62 (X_CopyArea)
Resource id: 0x740000f
X Error: BadPixmap (invalid Pixmap parameter) 4
Major opcode: 56 (X_ChangeGC)
Resource id: 0x0
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
Major opcode: 62 (X_CopyArea)
Resource id: 0x0
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
Major opcode: 55 (X_CreateGC)
Resource id: 0x0
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
Major opcode: 70 (X_PolyFillRectangle)
Resource id: 0x0
X Error: BadGC (invalid GC parameter) 13
Major opcode: 59 (X_SetClipRectangles)
Resource id: 0x0
X Error: BadGC (invalid GC parameter) 13
Major opcode: 56 (X_ChangeGC)
Resource id: 0x0
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
Major opcode: 70 (X_PolyFillRectangle)
Resource id: 0x0
X Error: BadGC (invalid GC parameter) 13
Major opcode: 60 (X_FreeGC)
Resource id: 0x0
X Error: BadMatch (invalid parameter attributes) 8
Major opcode: 62 (X_CopyArea)
Resource id: 0x740000f
X Error: BadPixmap (invalid Pixmap parameter) 4
Major opcode: 56 (X_ChangeGC)
Resource id: 0x0
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
Major opcode: 62 (X_CopyArea)
Resource id: 0x0
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
Major opcode: 55 (X_CreateGC)
Resource id: 0x0
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
Major opcode: 70 (X_PolyFillRectangle)
Resource id: 0x0
X Error: BadGC (invalid GC parameter) 13
Major opcode: 59 (X_SetClipRectangles)
Resource id: 0x0
X Error: BadGC (invalid GC parameter) 13
Major opcode: 56 (X_ChangeGC)
Resource id: 0x0
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
Major opcode: 70 (X_PolyFillRectangle)
Resource id: 0x0
X Error: BadGC (invalid GC parameter) 13
Major opcode: 60 (X_FreeGC)
Resource id: 0x0
X Error: BadMatch (invalid parameter attributes) 8
Major opcode: 62 (X_CopyArea)
Resource id: 0x740000f
Yep we are aware of them (didn't get around to figuring what was causing them), in regards to libboost it should be in the Libs folder which is already provided and referenced by the wrapper. Great to see the wallet works . |
|
|
|
|
e1ghtSpace
Legendary
Offline
Activity: 1526
Merit: 1001
Crypto since 2014
|
|
December 26, 2014, 09:43:09 PM |
|
I just started mining. I know someone else is also mining too. Nthused I assume.
Sorry for the diff rise I'm cutting down my hash rate now. 200 kh/s.
|
|
|
|
|
DenKoma
Member
Offline
Activity: 98
Merit: 10
|
|
December 26, 2014, 09:53:50 PM |
|
10 minutes before faucet start
360+ wallets downloaded
~100-110 coins estimated payout
|
|
|
|
DenKoma
Member
Offline
Activity: 98
Merit: 10
|
|
December 26, 2014, 10:00:42 PM |
|
196 coins - 1st payment was made as planned  |
|
|
|
mindrust
Legendary
Offline
Activity: 3290
Merit: 2448
|
|
December 26, 2014, 10:00:46 PM |
|
First payment has arrived. 196.07843137 FIND This is going to be good. It actually arrived 3 seconds before the countdown btw. |
.
.BLACKJACK ♠ FUN. | | | ███▄██████
██████████████▀
████████████
█████████████████
████████████████▄▄
░█████████████▀░▀▀
██████████████████
░██████████████
█████████████████▄
░██████████████▀
████████████
███████████████░██
██████████ | | CRYPTO CASINO &
SPORTS BETTING | | │ | | │ | ▄▄███████▄▄
▄███████████████▄
███████████████████
█████████████████████
███████████████████████
█████████████████████████
█████████████████████████
█████████████████████████
███████████████████████
█████████████████████
███████████████████
▀███████████████▀
███████████████████ | | .
|
|
|
|
|
fenghush
|
|
December 26, 2014, 10:01:13 PM |
|
I got my first coins 196 worth!
|
|
|
|
Nthused
Legendary
Offline
Activity: 1554
Merit: 1001
|
|
December 26, 2014, 10:02:11 PM |
|
Whoooo Hoooo first payment of 196.07843137 FIND Keep em coming |
|
|
|
|
|
doger69
|
|
December 26, 2014, 10:02:19 PM |
|
I got my first coins 196 worth!
Just got my first too Thanks for all the work guys,here we go all hahahah,this will be a fun ride  |
|
|
|
|
cakir
Legendary
Offline
Activity: 1274
Merit: 1000
★ BitClave ICO: 15/09/17 ★
|
|
December 26, 2014, 10:02:56 PM |
|
Wow! 204 wallets online! That's awesome guyz!
Keep up the good work!
|
|
|
|
|
|
|
,'#██+:
,█████████████'
+██████████████████
;██████████████████████
███████: .███████`
██████ ;█████'
`█████ #████#
████+ `████+
████: ████,
████: .# █ ████
;███+ ██ ███ ████
████ ███' ███. '███,
+███ #████ ,████ ████
████ █████ .+██████: █████+ `███.
,███ ███████████████████████ ████
████ ███████████████████████' :███
███: +████████████████████████ ███`
███ █████████████████████████` ███+
,███ ██████████████████████████ #███
'███ '██████████████████████████ ;███
#███ ███████████████████████████ ,███
████ ███████████████████████████. .███
████ ███████████████████████████' .███
+███ ███████████████████████████+ :███
:███ ███████████████████████████' +███
███ ███████████████████████████. ███#
███. #██████████████████████████ ███,
████ █████████████████████████+ `███
'███ '████████████████████████ ████
███; ███████████████████████ ███;
████ #████████████████████ ████
███# .██████████████████ `███+
████` ;██████████████ ████
████ '███████#. ████.
.████ █████
'████ █████
#████' █████
+█████` ██████
,██████: `███████
████████#;,..:+████████.
,███████████████████+
.███████████████;
`+███████#,
| |
|
|
|
|
