 Show Posts
|
|
Pages: [1] 2 »
|
Current plan for ShareSwap Module:
1) Redeem ac specified. Original asset specified.
2) Module loops through all original assets sent to redeem ac and for each one...
a) Module checks sender_account, transactionID, amount of assets
b) Module checks for replacement assets sent to sender ac with above transactionID as unencrypted message.
c) If not found, then send appropriate amount of assets to sender account with transaction ID as unencrypted message
3) Module is rerun a few hours or days later. Each time, it should check and then ignore transactions involving assets already swapped.
Module will be able to be run in a 'checking' mode which will report the assets which need to be sent, but not do any sending (won't do part c). This can be used first to make sure there's nothing weird going on.
Hoping to have something available for testing tomorrow. Any flaws in the above prodecure?
I don't see any problems with those steps. I don't have any Token on AE, but happy to test it with some other asset, or on test net. I'll be available in about 21 hours from the time I'm posting this (can never figure out what time that is in other places  |
|
|
|
I added auto BitcoinDark.conf generation today to the test repo.  Matthew Is that why I didn't need to do anything special on the most recent Mac wallet download I tested today? No, I only updated the source code. Haven't released a binary as it's still in development. I'm thinking we'll just have a list of trusted, donation-funded nodes hardcoded into the source. If you don't have a BitcoinDark.conf, it will automatically create it for you and generate a random rpcpassword. In that case there's almost no need for any installer anymore. Sounds nice! The only thing I can think of that you might need, is an option somewhere in the client to rebuild the database of blocks. That way a normal user never has to do something outside the client. |
|
|
|
Now that Windows and Mac builds are being worked on, we are days away from getting a release all put together for beta testing, so I need to get these last few things done in the next day or two
James
Just let me know when it's ready, and I'll create a new Windows Installer. |
|
|
|
the order in the .conf file doesnt matter
Good to know, but already found a better way to solve my problem . there should be different checksums for each binary download
if people are compiling their own, then the same version wont necessarily mean identical binaries due to differences in system build env
I used the version from the OP, as I haven't got a clue yet how to build it. Checksums were fine when I downloaded to a clean machine. Worked on the clean machine, and when finished created the SHA-256 checksum. Uploaded on my main machine. Downloaded on a 2nd clean machine, and still gave the same checksum. So I fugured all should be ok. it is a good idea about the general version number. not sure of the best way to have that across all OS and daemon and wallets
I would say that every release should have the same version on all platforms. Usually the first 3 numbers are/should be used for external releases, the forth number for internal builds. So everytime a version is released, update at least the 3rd number. Current version is 1.0.0.0, so next should be at least 1.0.1.0. I might (but still need to test that a bit further) even need the 2nd one to go up to keep the updates working as intended. If so, I'll keep using a different version for the installer only, just like I did now. |
|
|
|
Lets start with, please be carefull, only use at your own risk. I tried and used everything I could think of to keep this virus/malware free, but you never know. Hopefully we'll see the version of the .exe of the wallet increase when a new version arrives. Until then I'll use a different version for the installer (0.1.0 for this first one). This installer will: - Backup the %appdata%\BitcoinDark to %appdata%\BitcoinDark_<Date>_<Time>, and reuse the wallet.dat and BitcoinDark.conf if present. - Install the .exe in default location C:\Program Files\BitcoinDark or C:\Program Files (x86)\BitcoinDark on 64-bits systems. This is customizable in the wizard. - Will install the %appdata%\BitcoinDark\BitcoinDark.conf (if not present), with the rpcuser and rpcpassword both with random 32char UIDs. - Depending on the chosen settings, creates shortcuts in startmenu and/or desktop. - Give a warning if the wallet is still running, you have to close the wallet, to continue. (Did not find a better solution yet) Future installers will: - Do the same as this one - Uninstall older installations - Prevent older installers to overwrite the newer versions that I made Windows Installer version 0.1.0: Download hereSHA-256: 733603F0680A53EE247C2B995A78D0F8B1930B4644A6564FF431C6F9384CA9E6 Have fun! Qwitnix PS. last test took over an hour to get connections, but in the end it got there, so be patient. Edit: Tested on: Win8.1 64-bit Win7 64-bit Win7 32-bit |
|
|
|
I'm trying to run a wallet on windows, but nothing is happening... where should bitcoindark.conf be located: in same folder as exe or in data folder..??
is there some specific network settings that should be done..?
As far as I know, you should place the bitcoindark.conf in the C:\Users\<YourUserName>\AppData\Roaming\BitcoinDark folder. PS. I'm still working on the installer. Just need a bit more info and time. |
|
|
|
|
A few more questions about the wallet.
Is there a way to see if all lines of the BitcoinDark.conf are read without errors?
Is it ok to add a section head in the .conf like used in an ini file? [Settings] or something?
In the examples the .conf files all start with the rpcuser= and end with a list of the addnode=. Is it ok to mix up the sequence of the lines in the .conf? so start with a addnode= then the rpcuser= then another startnode= etc.
Is there a unique version number for each new version of the wallet?
if so, where can I find it?
if not, are you planning on doing that? It would be user friendly to have it, and I would like to try and use the same version numbers in the installer.
That's it for now.
Grtz,
Qwitnix
|
|
|
|
So rpcuser and rpcpassword should not be in the default .config, people that will need it, will have to add it manually?
Or should the installer ask for it?
I haven't got a clue what it's for so if included in the installer wizard, I need a text to explain it to a user and/or a default value.
Grtz,
Qwitnix
they are needed, if you can automatically generate some random values that would be perfect keep it to letters and numbers, 16 to 32 chars for each Ok, I'll try that. |
|
|
|
rpcuser=user
rpcpassword=pass
rpcport=14632
port=14631
daemon=1
gen=1
server=1
addnode=107.170.59.196
addnode=146.185.188.6
addnode=74.91.20.250:39997
addnode=54.85.50.15:50288
addnode=107.170.148.50:14631
addnode=65.129.66.246:57762
addnode=31.220.4.41
addnode=98.226.66.65
addnode=193.219.117.63
addnode=62.210.141.204
addnode=128.199.172.165
addnode=192.99.143.114
ths would be great! you should build the binary to make sure it is not infected, assuming your computer isnt infected i remember seeing checksum generating methods, but dont have the link the .conf file details will be changing with the new release, so for now, just use the second one here, with changes to the rpcuser and rpcpassword. i am assuming it wont be hard to update the .conf template So rpcuser and rpcpassword should not be in the default .config, people that will need it, will have to add it manually? Or should the installer ask for it? I haven't got a clue what it's for so if included in the installer wizard, I need a text to explain it to a user and/or a default value. Grtz, Qwitnix |
|
|
|
Hi all, I see quite some people having some troubles with the installation of the wallet. I myself also had some issues with the new version after the last fork. So I'm planning of making an installer for windows (.MSI) that will do: 1. Check if a previous version of this installer is installed, if so, uninstall the old one first / upgrade the old one. 2. If not (otherwise, in the future, this will be done by the uninstall of the old msipackage), check if wallet is running, if so kill process. Is there a way built into the wallet to close the wallet nicely from a commandline? 3. Place the .exe in a folder on C:\Program Files\BitcoinDark (location customizable in install wizard) 4. Place shortcut in startmenu (by default) 5. Place shortcut on desktop (Optional, not default, will be a checkbox on install) 6. Start .exe on windows startup (not the default option, will be a checkbox on install, will probably write a key in run under HKLM) 7. If exist, backup %appdata%\BitcoinDark to %appdata%\BitCoinDark_PrevVersion (if this already exsists, remove the old, create the new backup) and remove all in %appdata%\BitcoinDark, except wallet and .conf (Also optional, but default) 8. If not present create .conf in %appdata%\BitcoinDark 9. Start .exe when installation is finished (Optional, but default) To make this there's a few more things I need to know: If I include this .conf file as default, will that do for the general end-user (it is the one you can downloaded from OP)? addnode=107.170.59.196
addnode=146.185.188.6
addnode=74.91.20.250:39997
addnode=54.85.50.15:50288
addnode=186.94.211.104:49543
addnode=107.170.148.50:14631
addnode=65.129.66.246:57762
addnode=31.220.4.41
addnode=98.226.66.65
addnode=193.219.117.63
addnode=62.210.141.204
addnode=128.199.172.165
addnode=192.99.143.114
addnode=178.20.169.208
addnode=195.34.100.2:42038
addnode=5.101.107.239:60056
Or would it need the version that's written in text on the OP? rpcuser=user
rpcpassword=pass
rpcport=14632
port=14631
daemon=1
gen=1
server=1
addnode=107.170.59.196
addnode=146.185.188.6
addnode=74.91.20.250:39997
addnode=54.85.50.15:50288
addnode=107.170.148.50:14631
addnode=65.129.66.246:57762
addnode=31.220.4.41
addnode=98.226.66.65
addnode=193.219.117.63
addnode=62.210.141.204
addnode=128.199.172.165
addnode=192.99.143.114
Or maybe even a completely different one? How do I make sure that the file I upload is 100% virus, malware, etc free? Is there a trusted site or something? Is there a guide that I can follow to make a checksum thingy, so people can checkt it's the exact same thing I uploaded? Anything else needed? Grtz, Qwitnix tl;dr: Incoming windows installer, but need some input to make it work. |
|
|
|
|
Would love to do some testing, but again cannot seem to get any connections for days now...
|
|
|
|
I tried to generate 10,000 EXO after installation. So I pushed the button Generate 10,000 EXO and "clicked"... It tells me this one: You are not connected to the network.
Made I something wrong?
How can I connect to the network?
At the moment it seems it takes quite long to find an active connection. I had the same yesterday, left it alone for some time, and later I saw it had found 1 connection. Got a few blocks, and then I went to sleep =) |
|
|
|
tried to send 999.99 but the client sends 1000.88
888.998 889.88
888.889 888.7
111.991 112.81
11.9 11.9 ---- this is ok
11.199 11.199 --- this is ok
11.99 12.8
88.98 89.78
11.91 12
11.92 12.1
11.93 12.2
11.933 12.23
11.934 12.234
Confirmed, the first few give the same result here Had a similar thing with 1.001 1.1 1.01 1.1 |
|
|
|
|
Heya eXo_coin,
I sent you a PM with some bugs. Could you please look into at least the first 2?
Thanks,
Qwitnix
|
|
|
|
Wallet crashed when fiddling with signing (I still don't get how that works ... didn't set the message, used top adress from the drop down box, clicked ok, and it crashed. Can only reproduce this when I decrypt the wallet. When it's encrypted (the default when starting the wallet), it doesn't happen. |
|
|
|
Bug reportSent 1234 from EXOOBa8NeFF616dsOpBx97E4b8gsOds8bYQwcmee to EXOwqyBhpSsAGMUxm5s7Uu7SGDwkk3fA5MyHdbhc, transaction was valid and appeared in the transactionlist, wallet was debited and the receiving wallet was credited. After a minute the transaction disappeared on both wallets and amounts were restored... Hmmm, just found out that you could apply for the mail give-away even if you had already bought at the 1st and 2nd round... Didn't know that, I didn't apply  Are you sure? Did you remade that transaction? I can see it in the chain with: TX65E44025AB764EEA03CA149981C8A8F624A73CDE1742CAB041565638A9076377 please check... is our client still in sync? You can try to delete the chain and see if it will appear again as well pm me with your mail and I'll add you He did send it to me, and I had it in my wallet shortly... I send 1234 to him, then he send it back and my wallet showed 9999.90.. a minute or 2 later it was gone again. tested that again with another value 888.325, send that twice... one arrived... another resend of 888.325 now idd arrive. tested that again with another value 888.326, send that twice.... both in the chain... not sure what I did different this time.. note on the 888.325 and 888.326 - I had them all with the same Reference followed by a number... number 2 is missing, maybe you can see that somewhere? Also: I noticed some difference in the number of decimals..0 I'd suggest you use the same number of decimals in all fields... When I send 888.325xxxxxx till I couldn't type more, it was send as 888.325 in de chain and in the transactionlist. When I check my wallet, it said .70 where it should have been .705. When I checked in the blockchain, the total balance at the bottom of the search is .3, so only one decimal. That's all a bit confusing. |
|
|
|
|
Meh... agian too late for the Beta test... Would it be possible to have a testnet up inbetween te releases?
I understand it would need some restarts every now and then, but I keep missing the actual testing window, and I really would like to test it a bit.
|
|
|
|
|
Hi Anon136,
Just send you 1.009BTC (1BTC exo + 0.009 fee)
TransactionID: 5b55e5d0b5be44e89ed59fcf55945a39af466945c4e561fcb19fbc83046e1324
Thanks,
Qwitnix
|
|
|
|
|
