Topic: [TX]TRANSFER - BITTREX - MULTIPOOL - ANDROID - POS,TOR,MN, STEALTH - page 145. (Read 317969 times)
November 13, 2015, 04:11:28 PM
when is wallet out
November 11, 2015, 07:33:19 AM
I've created a windows build environment for anyone who may have had issues with building on windows before. I know I did myself, and it took quite a while to learn how to do it correctly.
The build environment include the QT5 files. Mingw49-32. and all of the dependencies needed to build transfercoin.
https://github.com/Infernoman/Transfercoin/releases/tag/WBE
There are some build instructions there as well.
The build environment include the QT5 files. Mingw49-32. and all of the dependencies needed to build transfercoin.
https://github.com/Infernoman/Transfercoin/releases/tag/WBE
There are some build instructions there as well.
Thanks for doing this infernoman. I will def give this a shot.
Edit: Please retweet https://twitter.com/Transfer_dev/status/664622773759700992
November 11, 2015, 07:22:24 AM
Give the link to the last Windows a wallet.
https://www.dropbox.com/s/m4g2eesngdpyo1w/transfer-1.2.0.0-win32.zip?dl=0
November 11, 2015, 05:17:37 AM
Give the link to the last Windows a wallet.
November 11, 2015, 03:30:16 AM
I've created a windows build environment for anyone who may have had issues with building on windows before. I know I did myself, and it took quite a while to learn how to do it correctly.
The build environment include the QT5 files. Mingw49-32. and all of the dependencies needed to build transfercoin.
https://github.com/Infernoman/Transfercoin/releases/tag/WBE
There are some build instructions there as well.
The build environment include the QT5 files. Mingw49-32. and all of the dependencies needed to build transfercoin.
https://github.com/Infernoman/Transfercoin/releases/tag/WBE
There are some build instructions there as well.
November 09, 2015, 01:58:41 PM
I start a wallet, there is a window:
In what reason?
In what reason?
Backup your wallet.dat. delete the data directory and resync. There have been some additions to the database in the last version and you need to resync to update.
The newest version currently released is V1.2-61401
Stealth addresses are fixed. And we're continuing forward. There's not too much left to do now. But test test test. I'll keep you guys updated if we find anything else
https://chainz.cryptoid.info/tx/block.dws?111662
As you can see in each of these transactions there is Nulldata which indicated a stealth address
November 09, 2015, 11:16:16 AM
I start a wallet, there is a window:
In what reason?
In what reason?
November 09, 2015, 09:24:29 AM
Im waiting for new release 
November 09, 2015, 09:02:55 AM
No problem at all, after typing out my messaage, I thought about the version change 
IOS wallet is under development now, partial payment for this has already been sent.
We are working on testing the other features in the wallet. In the process of updating darksend. Both Darksilk and Transfercoin have managed to break the stealth addresses lol. SOO we are working on getting that fixed over the next few days.
The cross sending and withdrawing from bittrex will require you to enter the password to your wallet IF its encrypted. Currently the api keys are NOT stored on disk. But since password protection has been implemented, it is something I am considering doing.
GetMinFee has been implemented which will allow for up to 50kb in FREE transactions. This also allows darksend transactions to the masternode to be processed without a fee.
I am hoping to have all of the work finished by next weekend and get the clients released. But if anyone is able to build and test a client send me a PM. And I will link you to my personal github branch where the work is taking place. Voting for the Hard fork has been locked at block 140 000, which leaves about ~20-30 days before the next fork.
IOS wallet is under development now, partial payment for this has already been sent.
We are working on testing the other features in the wallet. In the process of updating darksend. Both Darksilk and Transfercoin have managed to break the stealth addresses lol. SOO we are working on getting that fixed over the next few days.
The cross sending and withdrawing from bittrex will require you to enter the password to your wallet IF its encrypted. Currently the api keys are NOT stored on disk. But since password protection has been implemented, it is something I am considering doing.
GetMinFee has been implemented which will allow for up to 50kb in FREE transactions. This also allows darksend transactions to the masternode to be processed without a fee.
I am hoping to have all of the work finished by next weekend and get the clients released. But if anyone is able to build and test a client send me a PM. And I will link you to my personal github branch where the work is taking place. Voting for the Hard fork has been locked at block 140 000, which leaves about ~20-30 days before the next fork.
I wanted to bump this so it doesn't get overlooked.
Also I wanted to drop a note that I tested the new wallet last night with infernoman. I think everyone will like the added features.
I was able to get a full sync in just under an hour, over wireless. Below are the specs.
Intel Core i7
128GB SSD
8GB of RAM
November 08, 2015, 03:52:14 PM
good job ang good luck
Great work taking over the coin, I see a lot of potential for growth in the future. Since you are looking at a fork soon are you considering increasing the block size to meet future demand, this will also speed up the confirmation process and future proof the coin.
Thank you for the kind words. Also the current block size limit is already at 20x the current Bitcoin core. In the future I may increase the number of free transactions per block that can be accepted. Dependent on how the network grows.
November 08, 2015, 10:33:06 AM
good job ang good luck
November 08, 2015, 09:52:25 AM
hahaha. new coin? new free project? November 08, 2015, 04:04:43 AM
Great work taking over the coin, I see a lot of potential for growth in the future. Since you are looking at a fork soon are you considering increasing the block size to meet future demand, this will also speed up the confirmation process and future proof the coin.
November 07, 2015, 09:48:48 PM
Crytpotalklive interview with bitcoin_dad https://youtu.be/DVcrWR4QIsU
giving away 6000 TX
Edit: Good watch only about 24 minutes. Looks like @coinpromo won the 6000 $TX.
giving away 6000 TX
Edit: Good watch only about 24 minutes. Looks like @coinpromo won the 6000 $TX.
November 07, 2015, 12:33:52 PM
No problem at all, after typing out my messaage, I thought about the version change
IOS wallet is under development now, partial payment for this has already been sent.
We are working on testing the other features in the wallet. In the process of updating darksend. Both Darksilk and Transfercoin have managed to break the stealth addresses lol. SOO we are working on getting that fixed over the next few days.
The cross sending and withdrawing from bittrex will require you to enter the password to your wallet IF its encrypted. Currently the api keys are NOT stored on disk. But since password protection has been implemented, it is something I am considering doing.
GetMinFee has been implemented which will allow for up to 50kb in FREE transactions. This also allows darksend transactions to the masternode to be processed without a fee.
I am hoping to have all of the work finished by next weekend and get the clients released. But if anyone is able to build and test a client send me a PM. And I will link you to my personal github branch where the work is taking place. Voting for the Hard fork has been locked at block 140 000, which leaves about ~20-30 days before the next fork.
IOS wallet is under development now, partial payment for this has already been sent.
We are working on testing the other features in the wallet. In the process of updating darksend. Both Darksilk and Transfercoin have managed to break the stealth addresses lol. SOO we are working on getting that fixed over the next few days.
The cross sending and withdrawing from bittrex will require you to enter the password to your wallet IF its encrypted. Currently the api keys are NOT stored on disk. But since password protection has been implemented, it is something I am considering doing.
GetMinFee has been implemented which will allow for up to 50kb in FREE transactions. This also allows darksend transactions to the masternode to be processed without a fee.
I am hoping to have all of the work finished by next weekend and get the clients released. But if anyone is able to build and test a client send me a PM. And I will link you to my personal github branch where the work is taking place. Voting for the Hard fork has been locked at block 140 000, which leaves about ~20-30 days before the next fork.
November 05, 2015, 06:32:37 AM
I tried sending 10000 Tx out of my wallet and it made it freeze at block 91482, I went to check and repair my wallet and it comes up with a mismatch spent coins error:
23:04:32

checkwallet
23:04:32

{
"mismatched spent coins" : 1,
"amount in question" : 10000.00000000
}
23:04:58

repairwallet
23:04:58

{
"mismatched spent coins" : 1,
"amount affected by repair" : 10000.00000000
}
Not sure how to fix this issue, I have tried restarting the wallet, resyncing the wallet and everything else I can think of. Any ideas?
23:04:32

checkwallet
23:04:32

{
"mismatched spent coins" : 1,
"amount in question" : 10000.00000000
}
23:04:58

repairwallet
23:04:58

{
"mismatched spent coins" : 1,
"amount affected by repair" : 10000.00000000
}
Not sure how to fix this issue, I have tried restarting the wallet, resyncing the wallet and everything else I can think of. Any ideas?
Does the repairwallet command not fix your issue? If not then I'll need to look into the function to see what could be going wrong. A workaround for this. If repairwallet is not working, is you could dump the private keys for your wallet to a text file, then re import them. Also could you tell me which client version and protocol version you are running?
Open Debug console window and type resendtx. Sometimes it will resolve it.
if not, restoring an earlier backup of your wallet should do the trick has for me in the past with other coins
November 05, 2015, 03:39:34 AM
I tried sending 10000 Tx out of my wallet and it made it freeze at block 91482, I went to check and repair my wallet and it comes up with a mismatch spent coins error:
23:04:32

checkwallet
23:04:32

{
"mismatched spent coins" : 1,
"amount in question" : 10000.00000000
}
23:04:58

repairwallet
23:04:58

{
"mismatched spent coins" : 1,
"amount affected by repair" : 10000.00000000
}
Not sure how to fix this issue, I have tried restarting the wallet, resyncing the wallet and everything else I can think of. Any ideas?
23:04:32

checkwallet
23:04:32

{
"mismatched spent coins" : 1,
"amount in question" : 10000.00000000
}
23:04:58

repairwallet
23:04:58

{
"mismatched spent coins" : 1,
"amount affected by repair" : 10000.00000000
}
Not sure how to fix this issue, I have tried restarting the wallet, resyncing the wallet and everything else I can think of. Any ideas?
Does the repairwallet command not fix your issue? If not then I'll need to look into the function to see what could be going wrong. A workaround for this. If repairwallet is not working, is you could dump the private keys for your wallet to a text file, then re import them. Also could you tell me which client version and protocol version you are running?
Open Debug console window and type resendtx. Sometimes it will resolve it.
November 05, 2015, 12:53:52 AM
I tried sending 10000 Tx out of my wallet and it made it freeze at block 91482, I went to check and repair my wallet and it comes up with a mismatch spent coins error:
23:04:32

checkwallet
23:04:32

{
"mismatched spent coins" : 1,
"amount in question" : 10000.00000000
}
23:04:58

repairwallet
23:04:58

{
"mismatched spent coins" : 1,
"amount affected by repair" : 10000.00000000
}
Not sure how to fix this issue, I have tried restarting the wallet, resyncing the wallet and everything else I can think of. Any ideas?
23:04:32

checkwallet
23:04:32

{
"mismatched spent coins" : 1,
"amount in question" : 10000.00000000
}
23:04:58

repairwallet
23:04:58

{
"mismatched spent coins" : 1,
"amount affected by repair" : 10000.00000000
}
Not sure how to fix this issue, I have tried restarting the wallet, resyncing the wallet and everything else I can think of. Any ideas?
Does the repairwallet command not fix your issue? If not then I'll need to look into the function to see what could be going wrong. A workaround for this. If repairwallet is not working, is you could dump the private keys for your wallet to a text file, then re import them. Also could you tell me which client version and protocol version you are running?
November 02, 2015, 10:17:49 PM
When will we be able to download new wallet?
If your referring to the new QT wallets, I'm hoping to get them released in the next week or so. I'm trying to make sure everything has been updated correctly, and is functioning properly. I've been through the 0.11.2 github of dash's a few times over now, and we seem to keep finding things that have been missed, Now that darksend is actually working correctly, we can start focusing on other parts of the wallet. Once I am confident that the changes ive made are working correctly. which shouldnt be long, then i'll start asking others to swap to the new client, and get some beta testers for that.
PM me if you need any help compiling and or testing any wallets.
Edit: I finally bot my MacBook setup to compile the Qt wallet.
November 02, 2015, 07:44:00 PM
When will we be able to download new wallet?
If your referring to the new QT wallets, I'm hoping to get them released in the next week or so. I'm trying to make sure everything has been updated correctly, and is functioning properly. I've been through the 0.11.2 github of dash's a few times over now, and we seem to keep finding things that have been missed, Now that darksend is actually working correctly, we can start focusing on other parts of the wallet. Once I am confident that the changes ive made are working correctly. which shouldnt be long, then i'll start asking others to swap to the new client, and get some beta testers for that.
Jump to: