Bitcoin Forum
November 23, 2017, 02:07:48 AM *
News: Latest stable version of Bitcoin Core: 0.15.1  [Torrent].
 
   Home   Help Search Donate Login Register  
Pages: « 1 ... 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 [237] 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 »
  Print  
Author Topic: HoboNickels - HBN - High Fast Stake - Version 2.0! More Secure, Less Intensive  (Read 400799 times)
gildinglite
Member
**
Offline Offline

Activity: 98

These packets fly


View Profile
August 09, 2017, 01:39:55 AM
 #4721

"What do we want?", "HoboNickels!", "When do we want th...." -- said no one, ever.
1511402868
Hero Member
*
Offline Offline

Posts: 1511402868

View Profile Personal Message (Offline)

Ignore
1511402868
Reply with quote  #2

1511402868
Report to moderator
1511402868
Hero Member
*
Offline Offline

Posts: 1511402868

View Profile Personal Message (Offline)

Ignore
1511402868
Reply with quote  #2

1511402868
Report to moderator
1511402868
Hero Member
*
Offline Offline

Posts: 1511402868

View Profile Personal Message (Offline)

Ignore
1511402868
Reply with quote  #2

1511402868
Report to moderator
Join ICO Now Coinlancer is Disrupting the Freelance marketplace!
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1511402868
Hero Member
*
Offline Offline

Posts: 1511402868

View Profile Personal Message (Offline)

Ignore
1511402868
Reply with quote  #2

1511402868
Report to moderator
1511402868
Hero Member
*
Offline Offline

Posts: 1511402868

View Profile Personal Message (Offline)

Ignore
1511402868
Reply with quote  #2

1511402868
Report to moderator
1511402868
Hero Member
*
Offline Offline

Posts: 1511402868

View Profile Personal Message (Offline)

Ignore
1511402868
Reply with quote  #2

1511402868
Report to moderator
AztekPhoenix
Sr. Member
****
Offline Offline

Activity: 252


Rising from the Ashes


View Profile
August 09, 2017, 03:37:51 AM
 #4722

Why is synchronization now faster than before? One week passed in half hour Shocked

Small change to syncing in version 1.5.5.1, wouldn't think it would have that much effect. Usually the newest days are slower as there has to be more in depth test. The older back in the chain the faster the syncing is.

1.5.5.1 version
4 days synced very quickly, then it has refused to sync any further, restarts make no difference
This is what is in the debug log for hours without syncing anymore.

2017-08-09 02:41:30 Misbehaving: 173.244.48.198:53131 (3000 -> 3100) BAN THRESHOLD EXCEEDED
2017-08-09 02:41:30 ERROR: ProcessBlock() : block with too little proof-of-work
2017-08-09 02:41:30 Misbehaving: 173.244.48.198:53131 (3100 -> 3200) BAN THRESHOLD EXCEEDED
2017-08-09 02:41:30 ERROR: ProcessBlock() : block with too little proof-of-work
2017-08-09 02:41:30 Misbehaving: 173.244.48.198:53131 (3200 -> 3300) BAN THRESHOLD EXCEEDED
2017-08-09 02:41:30 ERROR: ProcessBlock() : block with too little proof-of-work
2017-08-09 02:41:30 Misbehaving: 173.244.48.198:53131 (3300 -> 3400) BAN THRESHOLD EXCEEDED
2017-08-09 02:41:30 ERROR: ProcessBlock() : block with too little proof-of-work
2017-08-09 02:41:30 Misbehaving: 173.244.48.198:53131 (3400 -> 3500) BAN THRESHOLD EXCEEDED
2017-08-09 02:41:30 ERROR: ProcessBlock() : block with too little proof-of-work
2017-08-09 02:41:30 ProcessBlock: ORPHAN BLOCK, prev=35cbc2069ff9a30d6cb4
2017-08-09 02:41:49 connection from 98.71.70.41:57555 dropped (banned)
2017-08-09 02:42:33 ping timeout: 1200.030000s
2017-08-09 02:42:38 connection from 92.30.32.29:63078 dropped (banned)
2017-08-09 02:42:52 connection from 104.207.128.75:63738 dropped (banned)
2017-08-09 02:44:52 connection from 104.230.143.200:33369 dropped (banned)


╥Aztek

Want Proof Lauda is a Pathetic fool , observe how she gives fake negative trust when she can't win a debate.  https://bitcointalk.org/index.php?action=trust;u=841833
Lauda is also an extortionist: https://bitcointalk.org/index.php?topic=1764757.msg17624090#msg17624090
Tranz
Legendary
*
Online Online

Activity: 1162


May the force bit with you.


View Profile
August 09, 2017, 05:25:58 AM
 #4723

Why is synchronization now faster than before? One week passed in half hour Shocked

Small change to syncing in version 1.5.5.1, wouldn't think it would have that much effect. Usually the newest days are slower as there has to be more in depth test. The older back in the chain the faster the syncing is.

1.5.5.1 version
4 days synced very quickly, then it has refused to sync any further, restarts make no difference
This is what is in the debug log for hours without syncing anymore.

2017-08-09 02:41:30 Misbehaving: 173.244.48.198:53131 (3000 -> 3100) BAN THRESHOLD EXCEEDED
2017-08-09 02:41:30 ERROR: ProcessBlock() : block with too little proof-of-work
2017-08-09 02:41:30 Misbehaving: 173.244.48.198:53131 (3100 -> 3200) BAN THRESHOLD EXCEEDED
2017-08-09 02:41:30 ERROR: ProcessBlock() : block with too little proof-of-work
2017-08-09 02:41:30 Misbehaving: 173.244.48.198:53131 (3200 -> 3300) BAN THRESHOLD EXCEEDED
2017-08-09 02:41:30 ERROR: ProcessBlock() : block with too little proof-of-work
2017-08-09 02:41:30 Misbehaving: 173.244.48.198:53131 (3300 -> 3400) BAN THRESHOLD EXCEEDED
2017-08-09 02:41:30 ERROR: ProcessBlock() : block with too little proof-of-work
2017-08-09 02:41:30 Misbehaving: 173.244.48.198:53131 (3400 -> 3500) BAN THRESHOLD EXCEEDED
2017-08-09 02:41:30 ERROR: ProcessBlock() : block with too little proof-of-work
2017-08-09 02:41:30 ProcessBlock: ORPHAN BLOCK, prev=35cbc2069ff9a30d6cb4
2017-08-09 02:41:49 connection from 98.71.70.41:57555 dropped (banned)
2017-08-09 02:42:33 ping timeout: 1200.030000s
2017-08-09 02:42:38 connection from 92.30.32.29:63078 dropped (banned)
2017-08-09 02:42:52 connection from 104.207.128.75:63738 dropped (banned)
2017-08-09 02:44:52 connection from 104.230.143.200:33369 dropped (banned)


╥Aztek

Hmmm. Would you mind to stop the client. Start it back up with the -debug flag passed to it. And then zip up the debug.log file and send it to me.  Not sure why this happened I will play around a bit with syncing with 1.5.5.1 to see if I can re-create.

HBN: https://bitcointalk.org/index.php?topic=303749.0
hobonickels.info HBN F1TranzWqFGZyFeTMu6iLbtTQgdXuJPsiL
daemonfox
Hero Member
*****
Offline Offline

Activity: 630



View Profile
August 09, 2017, 01:23:17 PM
 #4724

Tranz! Excellent work! 4 days of blocks synced in 25 seconds and I am up to date!

Staking now too.

Curious what made the difference here in this version... what parameters tweaked this?

EDIT: I would like to note one issue I see and IDK what the root cause is... I can go from 8+ connections syncing... to 2 connections when done and I have ALWAYS had to sit and wait for something to kick in for it to pick up peers again and catch the updated chain. This version just did it to me after I posted the above.

EDIT2: Log file https://drive.google.com/open?id=0B8Vvuskew8TmSDk1TWF4bk0xeGs

.ZenCash. █████
█████ ██
▀▀▀▀▀ ▀▀
▄▄▄ ███
▀▀▀ ▀▀▀
   ████
   ▀▀▀▀
███   ▄
███  ▄▄▄
   ▄▄ ███
  ▄
▄▄▄▄▄
    █████
██ █████
█████
█████ ██
▀▀▀▀▀ ▀▀
▄▄▄ ███
▀▀▀ ▀▀▀
   ████
   ▀▀▀▀
███   ▄
███  ▄▄▄
   ▄▄ ███
  ▄
▄▄▄▄▄
    █████
██ █████
slack   III   ANN Thread   III   Blog
Telegram   III   forum   III   twitter

▬▬▬▬▬▬▬▬▬▬▬▬▬  ZEN
forzendiablo
Legendary
*
Offline Offline

Activity: 1540


the grandpa of cryptos


View Profile
August 09, 2017, 02:01:04 PM
 #4725

yeah what is the main change in this built? its crazy how good it works now im really interested Smiley

yolo
daemonfox
Hero Member
*****
Offline Offline

Activity: 630



View Profile
August 09, 2017, 02:19:45 PM
 #4726

Just for funz and lulz I kicked off a fresh block sync with the new client.

Started at 10:18 AM EDT

.ZenCash. █████
█████ ██
▀▀▀▀▀ ▀▀
▄▄▄ ███
▀▀▀ ▀▀▀
   ████
   ▀▀▀▀
███   ▄
███  ▄▄▄
   ▄▄ ███
  ▄
▄▄▄▄▄
    █████
██ █████
█████
█████ ██
▀▀▀▀▀ ▀▀
▄▄▄ ███
▀▀▀ ▀▀▀
   ████
   ▀▀▀▀
███   ▄
███  ▄▄▄
   ▄▄ ███
  ▄
▄▄▄▄▄
    █████
██ █████
slack   III   ANN Thread   III   Blog
Telegram   III   forum   III   twitter

▬▬▬▬▬▬▬▬▬▬▬▬▬  ZEN
Turrican
Jr. Member
*
Offline Offline

Activity: 39


View Profile
August 09, 2017, 08:57:10 PM
 #4727

Version 1.5.5.1 run good ... put have many checkpoint error in the log

2017-08-09 20:41:13 ERROR: AcceptBlock() : rejected by synchronized checkpoint
2017-08-09 20:41:13 ERROR: ProcessBlock() : AcceptBlock FAILED

is the checkpoint on ?

[BTX]Bitcore
[HBN]HoboNickels
[OK]Okcash
Tranz
Legendary
*
Online Online

Activity: 1162


May the force bit with you.


View Profile
August 09, 2017, 10:33:12 PM
 #4728

Tranz! Excellent work! 4 days of blocks synced in 25 seconds and I am up to date!

Staking now too.

Curious what made the difference here in this version... what parameters tweaked this?

EDIT: I would like to note one issue I see and IDK what the root cause is... I can go from 8+ connections syncing... to 2 connections when done and I have ALWAYS had to sit and wait for something to kick in for it to pick up peers again and catch the updated chain. This version just did it to me after I posted the above.

EDIT2: Log file https://drive.google.com/open?id=0B8Vvuskew8TmSDk1TWF4bk0xeGs

Hey thanks.

So there does appear to be a invalid chain out there that some clients are getting caught up on.

Quote
2017-08-09 13:19:11 SetBestChain: new best=00000000050e13566f81 height=5499331 trust=85313787170553 blocktrust=12409 date=08/05/17 03:01:27
2017-08-09 13:19:11 ProcessBlock: ACCEPTED
2017-08-09 13:19:11 SetBestChain: new best=4eae80db8b34cfc616bd height=5499332 trust=85313804483242 blocktrust=17312689 date=08/05/17 03:02:33
2017-08-09 13:19:11 ProcessBlock: ACCEPTED

The block 5499331 is valid but from block 5499332 you are getting invalid blocks form a peer that is generating a completely invalid chain.  What is weird is that the checkpoint server was rejecting these and they shouldn't have made their way into chain, unless people are ignoring the checkpoints, which is allowed but not advisable.

I will update the block chain download on hobonickels.info which can be grabbed to get past the bad block. Give me till later tonight. I will also put some new hard-coded checkpoints in a release that I will try to get out here in the next day or so.  That should prevent any invalid chains from getting further propagated.

Also you said you were staking now? Can you send me your most current debug.log? No need to shutdown just send me what you have now. Also include you getpeerinfo rpc command output at the bottom or top please.


This the most current block as of typing this.

Quote
2017-08-09 22:36:14 SetBestChain: new best=000000000956f3c0dee8 height=5519496 trust=85607040993258 blocktrust=15361 date=08/09/17 22:35:50



HBN: https://bitcointalk.org/index.php?topic=303749.0
hobonickels.info HBN F1TranzWqFGZyFeTMu6iLbtTQgdXuJPsiL
Tranz
Legendary
*
Online Online

Activity: 1162


May the force bit with you.


View Profile
August 10, 2017, 02:57:10 AM
 #4729

Hi Everyone.

So there was definitely an invalid chain out there. I have a new release available that will prevent others from getting on that chain and continuing to propagate it.  It is now the default wallet to grab.

https://github.com/Tranz5/HoboNickels/releases/latest

If you are on the invalid chain you can try the new release, but the wallet will have a hard time getting back to the right chain. The easiest way will be to grab the block chain from hobonickels.info, and replace your txleveldb folder and blk0001.dat and blk0002.dat files and then bring up 1.5.5.2.

http://hobonickels.info/HBNBlockChain.zip

You can tell if you are on the right or wrong chain by looking at your wallets block browser.

Good blocks:
Code:
5499330 - aed47152a5cc2db3859dd9428089b8da1d0bdd445cd76e9711f3e304d727330f
5499331 - 00000000050e13566f81f688f2edd372415685b3c048d5b051457d170c2ea848
5499332 - 000000003806a3ee782ebc103bd7d7f47aeb753d4cce911a19dab453051e3ce5
5500000 - a8f0c882004f2f976ec8af49fa42c45620d4b33d7a1a95de748c9e19fc917962
5520337 - 0d464c4cb9c8f0b99ca2c432b820068d4fc37b3713cd881286db7787b5cda171

If you match those, keep on staking. If you don't stop and fix your block chain.

So how did this happen and what can be done?  Well I can only speculate as to why. But from what I see, during this time there was some flash mining going on. This may have caused some wallets to to lag and possibly disconnect from other node. Eventually they started to create their own chain. Usually when this happens, they eventually catch the real chain and then orphan all of their blocks. Why they didn't this time I can't say. Could be they were only connected to 1 other wallet, and they both simply kept on going.

What can be done. Well first off I will add more hard-coded checkpoints into each release.  Which will help. We are also going to slow down PoW in about 75,000 more blocks, and then 500,000 more after that PoW is gone. This will prevent flash mining and keep the network running more smoothly.  I am also going to move to 90 second (or higher) block time. This will again keep the network smoother and a single wallet will not be able to flash mine blocks with high weight.  Finally with the new release staking is now more efficient and the wallets will use less CPU so they will be able to keep up with the faster block time for now.


HBN: https://bitcointalk.org/index.php?topic=303749.0
hobonickels.info HBN F1TranzWqFGZyFeTMu6iLbtTQgdXuJPsiL
daemonfox
Hero Member
*****
Offline Offline

Activity: 630



View Profile
August 10, 2017, 04:15:21 AM
 #4730

Tranz! Excellent work! 4 days of blocks synced in 25 seconds and I am up to date!

Staking now too.

Curious what made the difference here in this version... what parameters tweaked this?

EDIT: I would like to note one issue I see and IDK what the root cause is... I can go from 8+ connections syncing... to 2 connections when done and I have ALWAYS had to sit and wait for something to kick in for it to pick up peers again and catch the updated chain. This version just did it to me after I posted the above.

EDIT2: Log file https://drive.google.com/open?id=0B8Vvuskew8TmSDk1TWF4bk0xeGs

Hey thanks.

So there does appear to be a invalid chain out there that some clients are getting caught up on.

Quote
2017-08-09 13:19:11 SetBestChain: new best=00000000050e13566f81 height=5499331 trust=85313787170553 blocktrust=12409 date=08/05/17 03:01:27
2017-08-09 13:19:11 ProcessBlock: ACCEPTED
2017-08-09 13:19:11 SetBestChain: new best=4eae80db8b34cfc616bd height=5499332 trust=85313804483242 blocktrust=17312689 date=08/05/17 03:02:33
2017-08-09 13:19:11 ProcessBlock: ACCEPTED

The block 5499331 is valid but from block 5499332 you are getting invalid blocks form a peer that is generating a completely invalid chain.  What is weird is that the checkpoint server was rejecting these and they shouldn't have made their way into chain, unless people are ignoring the checkpoints, which is allowed but not advisable.

I will update the block chain download on hobonickels.info which can be grabbed to get past the bad block. Give me till later tonight. I will also put some new hard-coded checkpoints in a release that I will try to get out here in the next day or so.  That should prevent any invalid chains from getting further propagated.

Also you said you were staking now? Can you send me your most current debug.log? No need to shutdown just send me what you have now. Also include you getpeerinfo rpc command output at the bottom or top please.


This the most current block as of typing this.

Quote
2017-08-09 22:36:14 SetBestChain: new best=000000000956f3c0dee8 height=5519496 trust=85607040993258 blocktrust=15361 date=08/09/17 22:35:50




Should have corrected that... at first post it appeared to be staking but when I swapped back after posting it had started balking at the bad block.

Giving the new version a try tomorrow.

.ZenCash. █████
█████ ██
▀▀▀▀▀ ▀▀
▄▄▄ ███
▀▀▀ ▀▀▀
   ████
   ▀▀▀▀
███   ▄
███  ▄▄▄
   ▄▄ ███
  ▄
▄▄▄▄▄
    █████
██ █████
█████
█████ ██
▀▀▀▀▀ ▀▀
▄▄▄ ███
▀▀▀ ▀▀▀
   ████
   ▀▀▀▀
███   ▄
███  ▄▄▄
   ▄▄ ███
  ▄
▄▄▄▄▄
    █████
██ █████
slack   III   ANN Thread   III   Blog
Telegram   III   forum   III   twitter

▬▬▬▬▬▬▬▬▬▬▬▬▬  ZEN
Turrican
Jr. Member
*
Offline Offline

Activity: 39


View Profile
August 10, 2017, 05:20:52 AM
 #4731

Open Console (In the Wallet click "Help/Debug windows/Console)

Tip in the Console :

getblockbynumber 5520337

and you have the "hash"

Good blocks:
Code:
5499330 - aed47152a5cc2db3859dd9428089b8da1d0bdd445cd76e9711f3e304d727330f
5499331 - 00000000050e13566f81f688f2edd372415685b3c048d5b051457d170c2ea848
5499332 - 000000003806a3ee782ebc103bd7d7f47aeb753d4cce911a19dab453051e3ce5
5500000 - a8f0c882004f2f976ec8af49fa42c45620d4b33d7a1a95de748c9e19fc917962
5520337 - 0d464c4cb9c8f0b99ca2c432b820068d4fc37b3713cd881286db7787b5cda171

ok ?  Smiley

Hi Everyone.

So there was definitely an invalid chain out there. I have a new release available that will prevent others from getting on that chain and continuing to propagate it.  It is now the default wallet to grab.

https://github.com/Tranz5/HoboNickels/releases/latest

If you are on the invalid chain you can try the new release, but the wallet will have a hard time getting back to the right chain. The easiest way will be to grab the block chain from hobonickels.info, and replace your txleveldb folder and blk0001.dat and blk0002.dat files and then bring up 1.5.5.2.

http://hobonickels.info/HBNBlockChain.zip

You can tell if you are on the right or wrong chain by looking at your wallets block browser.

Good blocks:
Code:
5499330 - aed47152a5cc2db3859dd9428089b8da1d0bdd445cd76e9711f3e304d727330f
5499331 - 00000000050e13566f81f688f2edd372415685b3c048d5b051457d170c2ea848
5499332 - 000000003806a3ee782ebc103bd7d7f47aeb753d4cce911a19dab453051e3ce5
5500000 - a8f0c882004f2f976ec8af49fa42c45620d4b33d7a1a95de748c9e19fc917962
5520337 - 0d464c4cb9c8f0b99ca2c432b820068d4fc37b3713cd881286db7787b5cda171

If you match those, keep on staking. If you don't stop and fix your block chain.

So how did this happen and what can be done?  Well I can only speculate as to why. But from what I see, during this time there was some flash mining going on. This may have caused some wallets to to lag and possibly disconnect from other node. Eventually they started to create their own chain. Usually when this happens, they eventually catch the real chain and then orphan all of their blocks. Why they didn't this time I can't say. Could be they were only connected to 1 other wallet, and they both simply kept on going.

What can be done. Well first off I will add more hard-coded checkpoints into each release.  Which will help. We are also going to slow down PoW in about 75,000 more blocks, and then 500,000 more after that PoW is gone. This will prevent flash mining and keep the network running more smoothly.  I am also going to move to 90 second (or higher) block time. This will again keep the network smoother and a single wallet will not be able to flash mine blocks with high weight.  Finally with the new release staking is now more efficient and the wallets will use less CPU so they will be able to keep up with the faster block time for now.



[BTX]Bitcore
[HBN]HoboNickels
[OK]Okcash
dnp
Full Member
***
Offline Offline

Activity: 151


View Profile
August 10, 2017, 07:11:08 AM
 #4732

windows qt v1.5.5.2 console/rpc directive
 validateaddress F1D7xQKugtYCDmKeZyNTqeGQxgutDcorXa
causes the program to fault

this is the first thing unomp mining pool software (i use unomp to solo mine multiple altcoins) does
when it connects

it seems if you feed validateaddress an invalid address it properly returns 'false'
but feed it a good address and the program fault happens

Doge:  DJSjip6DrpcbezVjJhfFdiDysU19J4MN5a            HoboNickels: ErCTkp3X91bUffC7kks1R1ee4hznJHxrNL 
Lotto:  LrJJSDckS7Ckud2koufxHjWJYnADn8MxSK        NoodlyAppendageCoin: NVVbnoFdWH3Xsw1oBu6g8LbuWcevGGzs3H
addnode=coins.dognose.com     ...for HOBO, MTLMC, NDL, PENG
HCLivess
Legendary
*
Offline Offline

Activity: 1344


[[[],[]],[[],[]]]


View Profile WWW
August 10, 2017, 12:18:52 PM
 #4733

I also noticed the fork, updating now. I like this tempo of development!

Bismuth - New Language, Interpretation Engines, Free Set of DAPPs https://bitcointalk.org/index.php?topic=1896497
Bitrated user: HCLivess.
Tranz
Legendary
*
Online Online

Activity: 1162


May the force bit with you.


View Profile
August 10, 2017, 01:11:55 PM
 #4734

windows qt v1.5.5.2 console/rpc directive
 validateaddress F1D7xQKugtYCDmKeZyNTqeGQxgutDcorXa
causes the program to fault

this is the first thing unomp mining pool software (i use unomp to solo mine multiple altcoins) does
when it connects

it seems if you feed validateaddress an invalid address it properly returns 'false'
but feed it a good address and the program fault happens


Seems to be working here? Did you compile yourself?


09:11:05

validateaddress F1D7xQKugtYCDmKeZyNTqeGQxgutDcorXa


09:11:05

{
"isvalid" : true,
"address" : "F1D7xQKugtYCDmKeZyNTqeGQxgutDcorXa",
"ismine" : false
}

HBN: https://bitcointalk.org/index.php?topic=303749.0
hobonickels.info HBN F1TranzWqFGZyFeTMu6iLbtTQgdXuJPsiL
Digi7ech
Member
**
Offline Offline

Activity: 113

HBN <3


View Profile
August 10, 2017, 07:30:32 PM
 #4735

Saw my 1.5.3 wallet was out of date foe about 8 days so just updated to 1.5.5.2 and downloaded the blockchain from your link.

It's up to date now but is saying none of my coins are aged yet, but they're all at least 15 days old. or did I miss a remark about coin age maturity changing?


///
Edit.
Just saw that my coin totals are off by waaay too much. Only saying I have 38k.

Hobo Nickel rocks!
HBN: ErCmri4PCGc1HAQtsufpWA7M1M9tjRdTb6
2xjO9M3P
Full Member
***
Offline Offline

Activity: 126


View Profile
August 10, 2017, 08:00:48 PM
 #4736

@Tranz
a preliminary potential bug report for a minor display bug. I will see if I can't find time this weekend to test further and write something more complete, assuming I haven't missed something obvious or stupid.

System: Ubuntu Server 16.04 x64, HoboNickels 1.5.5.0
Affected: listtransactions RPC

Reference:
named address, any address associated with an account
unnamed address, any address not associated with an account
change address, self-explanatory

Issue:
Code:
listtransactions
returns only transactions/stakes with named address
Code:
listtransactions ""
returns transactions/stakes with unnamed address

neither returns stakes created on change addresses, and I found no suitable RPC command to actually list these, outside of parsing blocks/transactions

Expected behaviour:
listtransaction lists all transactions regardless of the "type" of address

dnp
Full Member
***
Offline Offline

Activity: 151


View Profile
August 10, 2017, 09:08:45 PM
 #4737

Seems to be working here? Did you compile yourself?

no. downloaded from your repository
are there any dependency libs the QT may be finding on my system from years of older wallets?
or is the .exe totally self contained (well, except for the C runtime Smiley )


perhaps this weekend i can find some time to investigate and narrow things down further.
but as i type that validateaddress command into my console window, it faults and likewise
as UNOMP sends the same request it faults.

oh well, i'm sure it will reveal its true nature eventually Cheesy Smiley

ps: 64bit windoze 7 ultimate svc.pack 1, AMD phenom quad processor

Doge:  DJSjip6DrpcbezVjJhfFdiDysU19J4MN5a            HoboNickels: ErCTkp3X91bUffC7kks1R1ee4hznJHxrNL 
Lotto:  LrJJSDckS7Ckud2koufxHjWJYnADn8MxSK        NoodlyAppendageCoin: NVVbnoFdWH3Xsw1oBu6g8LbuWcevGGzs3H
addnode=coins.dognose.com     ...for HOBO, MTLMC, NDL, PENG
Tranz
Legendary
*
Online Online

Activity: 1162


May the force bit with you.


View Profile
August 10, 2017, 09:48:38 PM
 #4738

Saw my 1.5.3 wallet was out of date foe about 8 days so just updated to 1.5.5.2 and downloaded the blockchain from your link.

It's up to date now but is saying none of my coins are aged yet, but they're all at least 15 days old. or did I miss a remark about coin age maturity changing?


///
Edit.
Just saw that my coin totals are off by waaay too much. Only saying I have 38k.

Might just need to do a -rescan  Could take sometime so just wait until the debug.log says it is complete.


@Tranz
a preliminary potential bug report for a minor display bug. I will see if I can't find time this weekend to test further and write something more complete, assuming I haven't missed something obvious or stupid.

System: Ubuntu Server 16.04 x64, HoboNickels 1.5.5.0
Affected: listtransactions RPC

Reference:
named address, any address associated with an account
unnamed address, any address not associated with an account
change address, self-explanatory

Issue:
Code:
listtransactions
returns only transactions/stakes with named address
Code:
listtransactions ""
returns transactions/stakes with unnamed address

neither returns stakes created on change addresses, and I found no suitable RPC command to actually list these, outside of parsing blocks/transactions

Expected behaviour:
listtransaction lists all transactions regardless of the "type" of address


Hmmm I don't have any Stakes from Change, but I will try to generate some in test. Thanks for the report.
Seems to be working here? Did you compile yourself?

no. downloaded from your repository
are there any dependency libs the QT may be finding on my system from years of older wallets?
or is the .exe totally self contained (well, except for the C runtime Smiley )


perhaps this weekend i can find some time to investigate and narrow things down further.
but as i type that validateaddress command into my console window, it faults and likewise
as UNOMP sends the same request it faults.

oh well, i'm sure it will reveal its true nature eventually Cheesy Smiley

ps: 64bit windoze 7 ultimate svc.pack 1, AMD phenom quad processor


It is self contained. But possible if you have a .dll in your path it is trying to use it.  Do you have another user to try it under or just another simular machine to test. I have tested it on 3 different windows machines and seems to be work ok..

Edit: Ok I had it fail on me on a different machine. I will have a look here as soon as I can.

HBN: https://bitcointalk.org/index.php?topic=303749.0
hobonickels.info HBN F1TranzWqFGZyFeTMu6iLbtTQgdXuJPsiL
dnp
Full Member
***
Offline Offline

Activity: 151


View Profile
August 11, 2017, 12:06:03 AM
 #4739

validaddress fault is a BEX error?
a buffer overflow?

everything on google simply says put the program into the DEP exception list,
but that kinda ignores that it's a buffer overflow...


ps: i run under the cardinal sin. i have full admin privs when i run programs.

Doge:  DJSjip6DrpcbezVjJhfFdiDysU19J4MN5a            HoboNickels: ErCTkp3X91bUffC7kks1R1ee4hznJHxrNL 
Lotto:  LrJJSDckS7Ckud2koufxHjWJYnADn8MxSK        NoodlyAppendageCoin: NVVbnoFdWH3Xsw1oBu6g8LbuWcevGGzs3H
addnode=coins.dognose.com     ...for HOBO, MTLMC, NDL, PENG
Tranz
Legendary
*
Online Online

Activity: 1162


May the force bit with you.


View Profile
August 11, 2017, 12:27:10 AM
 #4740

validaddress fault is a BEX error?
a buffer overflow?

everything on google simply says put the program into the DEP exception list,
but that kinda ignores that it's a buffer overflow...


ps: i run under the cardinal sin. i have full admin privs when i run programs.


yes I am testing a fix right now.

HBN: https://bitcointalk.org/index.php?topic=303749.0
hobonickels.info HBN F1TranzWqFGZyFeTMu6iLbtTQgdXuJPsiL
Pages: « 1 ... 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 [237] 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!