Talking about the beta wallet:
there are a few graphics glitches when you move your mouse cursor over the GUI.
The colors are not very easily readable.
Everything else seems ok!
Topic: [ANN][SILKCOIN][DARKSILK PREANN][TESTING STORMNODES/DarkSIlk MARKET/I2P] - page 113. (Read 289507 times)
December 29, 2014, 11:27:02 AM
December 28, 2014, 03:47:33 PM
It's a while ago that i reading stuff about silk.
When i buy around a half year ago i liked this coin very much.
Before i set a buy-order i have a question. (reading 100 pages is a lot
)
Are there future plans for this coin and can somebody subscribe what kind of plans?
When i buy around a half year ago i liked this coin very much.
Before i set a buy-order i have a question. (reading 100 pages is a lot
)Are there future plans for this coin and can somebody subscribe what kind of plans?
There is some exciting upcoming plans but we dont want to make too much public at this stage (in case others steal our ideas/technologies)
Oke....
My buy-order got filled
.Thanks for the information,
December 28, 2014, 03:41:17 PM
It's a while ago that i reading stuff about silk.
When i buy around a half year ago i liked this coin very much.
Before i set a buy-order i have a question. (reading 100 pages is a lot)
Are there future plans for this coin and can somebody subscribe what kind of plans?
When i buy around a half year ago i liked this coin very much.
Before i set a buy-order i have a question. (reading 100 pages is a lot
)Are there future plans for this coin and can somebody subscribe what kind of plans?
There is some exciting upcoming plans but we dont want to make too much public at this stage (in case others steal our ideas/technologies)
December 28, 2014, 01:45:24 PM
It's a while ago that i reading stuff about silk.
When i buy around a half year ago i liked this coin very much.
Before i set a buy-order i have a question. (reading 100 pages is a lot)
Are there future plans for this coin and can somebody subscribe what kind of plans?
When i buy around a half year ago i liked this coin very much.
Before i set a buy-order i have a question. (reading 100 pages is a lot
)Are there future plans for this coin and can somebody subscribe what kind of plans?
December 28, 2014, 07:04:23 AM
May I ask why was my post deleted. What was wrong with the message?
Sorry man, can't post addies in thread or we can get banned. More then welcome to add your addy to your signature though!
December 27, 2014, 08:12:08 PM
Thats great!
The orphans are dropping right away which is great.
I removed over 2500 on my wallet!
The orphans are dropping right away which is great.
I removed over 2500 on my wallet!
December 27, 2014, 05:56:55 PM
December 27, 2014, 05:43:43 PM
May I ask why was my post deleted. What was wrong with the message?
December 27, 2014, 12:56:56 PM
I forgot to screen grab the orphans I cleared out so here is a festive camel marching onward to 2015 instead.
December 25, 2014, 10:34:35 AM
i also upgraded to the new wallet and did some clean up
Wallet looks great btw
16:28:53

Welcome to the Silkcoin RPC console.
Gebruik de pijltjestoetsen om door de geschiedenis te navigeren, en Ctrl-L om het scherm leeg te maken.
Typ help voor een overzicht van de beschikbare commando's.
16:29:12

checkwallet
16:30:13

{
"mismatched spent coins" : 0,
"amount in question" : 0.00000000,
"orphan blocks found" : 1497
}
16:30:25

repairwallet
16:33:22

{
"mismatched spent coins" : 0,
"amount affected by repair" : 0.00000000,
"orphan blocks removed" : 1497
}
Wallet looks great btw
16:28:53

Welcome to the Silkcoin RPC console.
Gebruik de pijltjestoetsen om door de geschiedenis te navigeren, en Ctrl-L om het scherm leeg te maken.
Typ help voor een overzicht van de beschikbare commando's.
16:29:12

checkwallet
16:30:13

{
"mismatched spent coins" : 0,
"amount in question" : 0.00000000,
"orphan blocks found" : 1497
}
16:30:25

repairwallet
16:33:22

{
"mismatched spent coins" : 0,
"amount affected by repair" : 0.00000000,
"orphan blocks removed" : 1497
}
December 25, 2014, 04:46:19 AM
Merry xmas fellow camel riders!!!!
Hope you all have a great day !!!
Remember your wives would love a bit of SILK for xmas buy buy
Q
Hope you all have a great day !!!
Remember your wives would love a bit of SILK for xmas buy buy
Q
December 24, 2014, 06:37:41 PM
The curious incident of the coins in the night-time.
I sent some coins to an empty wallet using the previous version of the software.
They failed to arrive, although the send was confirmed many times.
Cutting a long story (and many hours of frustration) short...
The destination wallet.dat was created using the previous software, but running in the new software with a fresh download of the blockchain. It was empty before the upgrade.
As a final resort I copied the destination wallet.dat to the machine running the previous software, and placed it in the silk data folder.
When it eventually synchronised the coins appeared. They were still not showing in the same wallet.dat running with the latest version.
So I copied the destination wallet from the machine with the previous version to the machine running the current version.
Having registered with the wallet.dat under the previous version... the coins were now present and correct under the new version.
So I have Two Copies of the same wallet.dat (created with the previous version and containing the same addresses).
One copy was empty when I upgraded to the latest software and refuses to see coins sent to addresses in that wallet.
The other copy was empty until I ran it using the previous software, when it registere receipt of the coins.
The sending wallet was running under the old software.
The coins sent to this wallet.dat will not register under the latest software until they have registered with the software version that created it.
I have not conducted any more tests, but it would seem that the addresses in a wallet created by the previous software need to be initialised by receiving coins under that version before they will function correctly with the new version. The copy that has not been running under the previous version (since the coins were sent) is still reporting that it is empty under the new version.
This could cause compatibility issues with upgrades, so I'm hoping that the team will investigate. Sorry about the longwinded account.
I sent some coins to an empty wallet using the previous version of the software.
They failed to arrive, although the send was confirmed many times.
Cutting a long story (and many hours of frustration) short...
The destination wallet.dat was created using the previous software, but running in the new software with a fresh download of the blockchain. It was empty before the upgrade.
As a final resort I copied the destination wallet.dat to the machine running the previous software, and placed it in the silk data folder.
When it eventually synchronised the coins appeared. They were still not showing in the same wallet.dat running with the latest version.
So I copied the destination wallet from the machine with the previous version to the machine running the current version.
Having registered with the wallet.dat under the previous version... the coins were now present and correct under the new version.
So I have Two Copies of the same wallet.dat (created with the previous version and containing the same addresses).
One copy was empty when I upgraded to the latest software and refuses to see coins sent to addresses in that wallet.
The other copy was empty until I ran it using the previous software, when it registere receipt of the coins.
The sending wallet was running under the old software.
The coins sent to this wallet.dat will not register under the latest software until they have registered with the software version that created it.
I have not conducted any more tests, but it would seem that the addresses in a wallet created by the previous software need to be initialised by receiving coins under that version before they will function correctly with the new version. The copy that has not been running under the previous version (since the coins were sent) is still reporting that it is empty under the new version.
This could cause compatibility issues with upgrades, so I'm hoping that the team will investigate. Sorry about the longwinded account.
hmm why did you use an empty wallet.DAT from old in new then send old coins to old wallet in new client? lol that's some kind of riddle..
As explained in a previous post, I used to clean up my wallets by sending coins to a fresh wallet. I had one set up when the upgrade was issued so I used it with the new software and a fresh copy of the blockchain rather than setting up a new wallet from scratch. No orphans, redundant receiving addresses, or fragmented staking.
personally I just kept my old wallet while running the new beta exe.
have you checked wallet for any mismatched coins?
kinda sounds like using 2 different wallet.dats with different balances on 2 different versions might cause issues lol
The same Wallet.dat on two different versions. When the coins didn't arrive I tried numerous remedies before I thought of copying the wallet back into the old software which generated it. The coins arrived when I opened the wallet with the old software, and when I switched That copy to the new software they were fine. But I still have a copy of the same wallet that has not been used with the old software since the coins were transferred. This copy will not register the coins.
Try it for yourself.
Have a sending wallet running with the old software. Generate a new receiving wallet using the old software, and then run it using the new software. Send some coins to the receiving wallet and wait for them to arrive. If they don't, then copy the receiving wallet.dat to the machine running the old software and see them arrive. Then copy the receiving wallet back to the machine running the new software having first made a backup copy of of the wallet.dat that refused to see the coins. The copy that's been run through the old software should contain the coins from the sending wallet... but the copy that hasn't been run through the old software will refuse to do so.
The addresses in Both copies are identical. So why won't the copy that hasn't
It's an obscure but interesting scenario that only cane to light by accident. It 'might' have an impact on upgrades if an old wallet.dat is used (as frequently happens) with upgraded software. It only seems to affect wallets that have not been used at all before an upgrade, but I haven't investigated in greater depth. If it affects receiving addresses that haven't been used prior to the upgrade then there could be more serious ramifications... particularly after a hard fork, when 'fixing' the wallet by running the software that generated it is no longer an option.
It may well be an issue that affects other coins. I'll look around for some with recently upgraded wallets and give it a try. I now have both versions of silkcoin set up on one machine, each with it's own copy of the blockchain (not using default locations). You can't run them together because of a conflict accessing ports, but they run quite normally using either/or.
unless you talking about two different computers then this might make more sense.
you in silkchat? welcome to pm me and we can talk more.
sooo is there missing coins? I'm sorry couldn't really find for sure if that was the case in the post, lol but its christmas eve and Santa has rum haha
haha that quoting was as cryptic as the explaination lol.. but here goes
1. create new recieving address in old wallet then send to that receiving address in new client with old wallet installed.
2. send coins from old client to new client with old wallet installed based on the receiving address you created in old wallet
3. say wtf are my coins?
haha well to me looks like a coin control issue. u can create as many addies as ya want but they all are the same wallet.DAT
personally I am still learning coin control as there isnt much resources I've found in plain German lol so once I fully grasp and really anyone else who has knowledge of qt and bitcoind silkcoin d etc create a video knowledge base so silk comm gets real fucking smart.
I mean Obama is doing it with hour of code.. why can't silk comm all become knowledgeable in as many aspects of the client as possible.
again well does the orphan removal tool aid the community? well yes. cuz we are all learning (sorry maybe not all haha) how to use the client. the strength of a network not only lies in its connections but also in the understanding of a conection and our role in the network.
but yeh man check into this scenario with other coins. and will have to make clear instructions if this strange thing in the night haha is something to cause user adoptance issues.
after all a happy network is happy nodes and happy nodes are silky. (-;
December 24, 2014, 05:58:44 PM
The curious incident of the coins in the night-time.
I sent some coins to an empty wallet using the previous version of the software.
They failed to arrive, although the send was confirmed many times.
Cutting a long story (and many hours of frustration) short...
The destination wallet.dat was created using the previous software, but running in the new software with a fresh download of the blockchain. It was empty before the upgrade.
As a final resort I copied the destination wallet.dat to the machine running the previous software, and placed it in the silk data folder.
When it eventually synchronised the coins appeared. They were still not showing in the same wallet.dat running with the latest version.
So I copied the destination wallet from the machine with the previous version to the machine running the current version.
Having registered with the wallet.dat under the previous version... the coins were now present and correct under the new version.
So I have Two Copies of the same wallet.dat (created with the previous version and containing the same addresses).
One copy was empty when I upgraded to the latest software and refuses to see coins sent to addresses in that wallet.
The other copy was empty until I ran it using the previous software, when it registere receipt of the coins.
The sending wallet was running under the old software.
The coins sent to this wallet.dat will not register under the latest software until they have registered with the software version that created it.
I have not conducted any more tests, but it would seem that the addresses in a wallet created by the previous software need to be initialised by receiving coins under that version before they will function correctly with the new version. The copy that has not been running under the previous version (since the coins were sent) is still reporting that it is empty under the new version.
This could cause compatibility issues with upgrades, so I'm hoping that the team will investigate. Sorry about the longwinded account.
I sent some coins to an empty wallet using the previous version of the software.
They failed to arrive, although the send was confirmed many times.
Cutting a long story (and many hours of frustration) short...
The destination wallet.dat was created using the previous software, but running in the new software with a fresh download of the blockchain. It was empty before the upgrade.
As a final resort I copied the destination wallet.dat to the machine running the previous software, and placed it in the silk data folder.
When it eventually synchronised the coins appeared. They were still not showing in the same wallet.dat running with the latest version.
So I copied the destination wallet from the machine with the previous version to the machine running the current version.
Having registered with the wallet.dat under the previous version... the coins were now present and correct under the new version.
So I have Two Copies of the same wallet.dat (created with the previous version and containing the same addresses).
One copy was empty when I upgraded to the latest software and refuses to see coins sent to addresses in that wallet.
The other copy was empty until I ran it using the previous software, when it registere receipt of the coins.
The sending wallet was running under the old software.
The coins sent to this wallet.dat will not register under the latest software until they have registered with the software version that created it.
I have not conducted any more tests, but it would seem that the addresses in a wallet created by the previous software need to be initialised by receiving coins under that version before they will function correctly with the new version. The copy that has not been running under the previous version (since the coins were sent) is still reporting that it is empty under the new version.
This could cause compatibility issues with upgrades, so I'm hoping that the team will investigate. Sorry about the longwinded account.
hmm why did you use an empty wallet.DAT from old in new then send old coins to old wallet in new client? lol that's some kind of riddle..
As explained in a previous post, I used to clean up my wallets by sending coins to a fresh wallet. I had one set up when the upgrade was issued so I used it with the new software and a fresh copy of the blockchain rather than setting up a new wallet from scratch. No orphans, redundant receiving addresses, or fragmented staking.
personally I just kept my old wallet while running the new beta exe.
have you checked wallet for any mismatched coins?
kinda sounds like using 2 different wallet.dats with different balances on 2 different versions might cause issues lol
The same Wallet.dat on two different versions. When the coins didn't arrive I tried numerous remedies before I thought of copying the wallet back into the old software which generated it. The coins arrived when I opened the wallet with the old software, and when I switched That copy to the new software they were fine. But I still have a copy of the same wallet that has not been used with the old software since the coins were transferred. This copy will not register the coins.
Try it for yourself.
Have a sending wallet running with the old software. Generate a new receiving wallet using the old software, and then run it using the new software. Send some coins to the receiving wallet and wait for them to arrive. If they don't, then copy the receiving wallet.dat to the machine running the old software and see them arrive. Then copy the receiving wallet back to the machine running the new software having first made a backup copy of of the wallet.dat that refused to see the coins. The copy that's been run through the old software should contain the coins from the sending wallet... but the copy that hasn't been run through the old software will refuse to do so.
The addresses in Both copies are identical. So why won't the copy that hasn't
It's an obscure but interesting scenario that only cane to light by accident. It 'might' have an impact on upgrades if an old wallet.dat is used (as frequently happens) with upgraded software. It only seems to affect wallets that have not been used at all before an upgrade, but I haven't investigated in greater depth. If it affects receiving addresses that haven't been used prior to the upgrade then there could be more serious ramifications... particularly after a hard fork, when 'fixing' the wallet by running the software that generated it is no longer an option.
It may well be an issue that affects other coins. I'll look around for some with recently upgraded wallets and give it a try. I now have both versions of silkcoin set up on one machine, each with it's own copy of the blockchain (not using default locations). You can't run them together because of a conflict accessing ports, but they run quite normally using either/or.
unless you talking about two different computers then this might make more sense.
you in silkchat? welcome to pm me and we can talk more.
sooo is there missing coins? I'm sorry couldn't really find for sure if that was the case in the post, lol but its christmas eve and Santa has rum haha
December 24, 2014, 05:08:32 PM
hmm yes so checked it out and im finding different locations on the screen will allow to minimize and not minimize.
I'm going to try and recreate some more and see if it is location based which would seem unlikely or cpu fluctuations causing a glitch?
lol its a good beta find anyways. if anyone solves it before us I'll have a bounty waiting.
are any nix users experiencing this is it just ol winblows at her dirty tricks again?
It looks like the issue is if any part of the wallet is off the screen it will not minimize. Most likely trying to store a value out of range that would be used when the wallet/window is restored. Any case if any part of the wallet is out of the view area of the screen it does not minimize. Once all parts of the wallet are visible it can be minimized.
December 24, 2014, 04:57:06 PM
hahaha stolen post from Mauricio in hipchat!
silk in bloomberg...
silk in bloomberg...
December 24, 2014, 04:48:41 PM
I don't know why, but the minimize window button is not working in last couple of wallets, is it like that for everyone?
I have noticed that if you move the wallet on your desktop ( left right up down) the minimize button will work in some places but not others.
am on win 7 64bit if this helps
if i drag it back to the center of the screen it works fine
Q
I was just checking this out and the patter is if the edge of the wallet is off the screen it will not minimize. If the whole wallet is within your screen it will minimize but it will not minimize if any part of the wallet is outside of your screen viewing area.
hmm yes so checked it out and im finding different locations on the screen will allow to minimize and not minimize.
I'm going to try and recreate some more and see if it is location based which would seem unlikely or cpu fluctuations causing a glitch?
lol its a good beta find anyways. if anyone solves it before us I'll have a bounty waiting.
are any nix users experiencing this is it just ol winblows at her dirty tricks again?
December 24, 2014, 04:45:50 PM
The curious incident of the coins in the night-time.
I sent some coins to an empty wallet using the previous version of the software.
They failed to arrive, although the send was confirmed many times.
Cutting a long story (and many hours of frustration) short...
The destination wallet.dat was created using the previous software, but running in the new software with a fresh download of the blockchain. It was empty before the upgrade.
As a final resort I copied the destination wallet.dat to the machine running the previous software, and placed it in the silk data folder.
When it eventually synchronised the coins appeared. They were still not showing in the same wallet.dat running with the latest version.
So I copied the destination wallet from the machine with the previous version to the machine running the current version.
Having registered with the wallet.dat under the previous version... the coins were now present and correct under the new version.
So I have Two Copies of the same wallet.dat (created with the previous version and containing the same addresses).
One copy was empty when I upgraded to the latest software and refuses to see coins sent to addresses in that wallet.
The other copy was empty until I ran it using the previous software, when it registere receipt of the coins.
The sending wallet was running under the old software.
The coins sent to this wallet.dat will not register under the latest software until they have registered with the software version that created it.
I have not conducted any more tests, but it would seem that the addresses in a wallet created by the previous software need to be initialised by receiving coins under that version before they will function correctly with the new version. The copy that has not been running under the previous version (since the coins were sent) is still reporting that it is empty under the new version.
This could cause compatibility issues with upgrades, so I'm hoping that the team will investigate. Sorry about the longwinded account.
I sent some coins to an empty wallet using the previous version of the software.
They failed to arrive, although the send was confirmed many times.
Cutting a long story (and many hours of frustration) short...
The destination wallet.dat was created using the previous software, but running in the new software with a fresh download of the blockchain. It was empty before the upgrade.
As a final resort I copied the destination wallet.dat to the machine running the previous software, and placed it in the silk data folder.
When it eventually synchronised the coins appeared. They were still not showing in the same wallet.dat running with the latest version.
So I copied the destination wallet from the machine with the previous version to the machine running the current version.
Having registered with the wallet.dat under the previous version... the coins were now present and correct under the new version.
So I have Two Copies of the same wallet.dat (created with the previous version and containing the same addresses).
One copy was empty when I upgraded to the latest software and refuses to see coins sent to addresses in that wallet.
The other copy was empty until I ran it using the previous software, when it registere receipt of the coins.
The sending wallet was running under the old software.
The coins sent to this wallet.dat will not register under the latest software until they have registered with the software version that created it.
I have not conducted any more tests, but it would seem that the addresses in a wallet created by the previous software need to be initialised by receiving coins under that version before they will function correctly with the new version. The copy that has not been running under the previous version (since the coins were sent) is still reporting that it is empty under the new version.
This could cause compatibility issues with upgrades, so I'm hoping that the team will investigate. Sorry about the longwinded account.
hmm why did you use an empty wallet.DAT from old in new then send old coins to old wallet in new client? lol that's some kind of riddle..
personally I just kept my old wallet while running the new beta exe.
have you checked wallet for any mismatched coins?
kinda sounds like using 2 different wallet.dats with different balances on 2 different versions might cause issues lol
unless you talking about two different computers then this might make more sense.
you in silkchat? welcome to pm me and we can talk more.
sooo is there missing coins? I'm sorry couldn't really find for sure if that was the case in the post, lol but its christmas eve and Santa has rum haha
December 24, 2014, 12:26:34 PM
The curious incident of the coins in the night-time.
I sent some coins to an empty wallet using the previous version of the software.
They failed to arrive, although the send was confirmed many times.
Cutting a long story (and many hours of frustration) short...
The destination wallet.dat was created using the previous software, but running in the new software with a fresh download of the blockchain. It was empty before the upgrade.
As a final resort I copied the destination wallet.dat to the machine running the previous software, and placed it in the silk data folder.
When it eventually synchronised the coins appeared. They were still not showing in the same wallet.dat running with the latest version.
So I copied the destination wallet from the machine with the previous version to the machine running the current version.
Having registered with the wallet.dat under the previous version... the coins were now present and correct under the new version.
So I have Two Copies of the same wallet.dat (created with the previous version and containing the same addresses).
One copy was empty when I upgraded to the latest software and refuses to see coins sent to addresses in that wallet.
The other copy was empty until I ran it using the previous software, when it registere receipt of the coins.
The sending wallet was running under the old software.
The coins sent to this wallet.dat will not register under the latest software until they have registered with the software version that created it.
I have not conducted any more tests, but it would seem that the addresses in a wallet created by the previous software need to be initialised by receiving coins under that version before they will function correctly with the new version. The copy that has not been running under the previous version (since the coins were sent) is still reporting that it is empty under the new version.
This could cause compatibility issues with upgrades, so I'm hoping that the team will investigate. Sorry about the longwinded account.
I sent some coins to an empty wallet using the previous version of the software.
They failed to arrive, although the send was confirmed many times.
Cutting a long story (and many hours of frustration) short...
The destination wallet.dat was created using the previous software, but running in the new software with a fresh download of the blockchain. It was empty before the upgrade.
As a final resort I copied the destination wallet.dat to the machine running the previous software, and placed it in the silk data folder.
When it eventually synchronised the coins appeared. They were still not showing in the same wallet.dat running with the latest version.
So I copied the destination wallet from the machine with the previous version to the machine running the current version.
Having registered with the wallet.dat under the previous version... the coins were now present and correct under the new version.
So I have Two Copies of the same wallet.dat (created with the previous version and containing the same addresses).
One copy was empty when I upgraded to the latest software and refuses to see coins sent to addresses in that wallet.
The other copy was empty until I ran it using the previous software, when it registere receipt of the coins.
The sending wallet was running under the old software.
The coins sent to this wallet.dat will not register under the latest software until they have registered with the software version that created it.
I have not conducted any more tests, but it would seem that the addresses in a wallet created by the previous software need to be initialised by receiving coins under that version before they will function correctly with the new version. The copy that has not been running under the previous version (since the coins were sent) is still reporting that it is empty under the new version.
This could cause compatibility issues with upgrades, so I'm hoping that the team will investigate. Sorry about the longwinded account.
December 24, 2014, 06:41:56 AM
I don't know why, but the minimize window button is not working in last couple of wallets, is it like that for everyone?
I have noticed that if you move the wallet on your desktop ( left right up down) the minimize button will work in some places but not others.
am on win 7 64bit if this helps
if i drag it back to the center of the screen it works fine
Q
I was just checking this out and the patter is if the edge of the wallet is off the screen it will not minimize. If the whole wallet is within your screen it will minimize but it will not minimize if any part of the wallet is outside of your screen viewing area.
December 24, 2014, 06:34:26 AM
I don't know why, but the minimize window button is not working in last couple of wallets, is it like that for everyone?
I have noticed that if you move the wallet on your desktop ( left right up down) the minimize button will work in some places but not others.
am on win 7 64bit if this helps
if i drag it back to the center of the screen it works fine
Q
Jump to: