Quote from: Akado on September 06, 2015, 01:26:52 PM
You have to wait till it syncs, also:

Quote from: DataSecurityNode on September 06, 2015, 01:19:45 PM

If you would like to have a more trouble free experience I recommend setting up a wallet at:

https://wallet.bitshares.org

Now I have " Severe network problems | Not connected " in https://wallet.bitshares.org :/   ... is there any general bad weather ? or it's just my account's bad luck ?

Quote from: vikram on January 24, 2015, 09:59:20 PM

Quote from: liondani on January 24, 2015, 09:20:23 PM
@dannotestein
It would be much better you change the output from:

"You offered us a block...."

to

"This peer offered us a block..."

because the message is misleading and anybody that reads it, thinks he has a problem himself ...
That was the case with me too the first time I had read it  :)

In this case the other client is disconnecting us because we are offering it invalid blocks, so the message makes sense.

This is different from us disconnecting another client because it is offering us invalid blocks, which has a different message.

Thanks everybody for the explanations I'm understanding more bitshares ecosystem thanks to all of you.

I have a git pull from Saturday  so I'm assuming I have a newer version than my peer.

About messages... now I get:


Peer 180.168.198.173:60086 disconnected us: You offered me a list of more sync blocks than could possibly exist
[/cod]

I guess this falls into the same category of version discrepancy. Sadly I assume network_get_peer_info wont show him since it has been disconnected. Is there a way to see "older"(disconnected) peers?

Hi I'm getting a


Peer 178.143.67.69:29235 disconnected us: You offered us a block that we reject as invalid
Peer 178.143.67.69:10585 disconnected us: You offered us a block that we reject as invalid
Peer 178.143.67.69:11637 disconnected us: You offered us a block that we reject as invalid
Peer 178.143.67.69:12823 disconnected us: You offered us a block that we reject as invalid


Any idea what could this be?

EDIT (short answer): @dannotestein summarized: "If you're running a new client, it means this other client is an older one and you have nothing to worry about (the other guy needs to update his client). If you're not running a new client, you probably need to update.". Thx @xeroc for the answer too

Thanks,
Nico Cesar

Quote from: wackou on January 24, 2015, 10:44:14 AM

Code Select Expand


wallet_account_update_registration delegate.nicocesar nicocesar null 3


great explanation wackou!! thanks for your time. But seems that I lost all my credits doing a 2nd register instead of the delegate promotion .... right?


bitsharewallet (unlocked) >>> wallet_account_update_registration delegate.nicocesar nicocesar null 3
0 exception: unspecified
Unable to pay fee; no remaining balances can cover it and no account can pay it.


BTW,  do you think 3% is good enough?

Great work!!! I'm just getting into the community and your webpage helped me a lot!! thanks! 

about SEO, there are some free tools that help to give a quick bullet list of things to improve: https://www.lipperhey.com/en/analysis/quick/ most of them take 2 minutes to fix.

Quote from: onceuponatime on January 23, 2015, 07:12:32 AM
Maybe this will give you something to try?
https://bitsharestalk.org/index.php?topic=13606.msg177581#msg177581


If that is not it you should start a new thread here describing your problem and what you have done so far to get some tech help:
https://bitsharestalk.org/index.php?board=45.0

Ok updated to lates git pull and some stuff is working  .... like the blockchain is now in sync


bitsharewallet (unlocked) >>> wallet_list_my_accounts
NAME (* delegate)                  KEY                                                             REGISTERED            FAVORITE       APPROVAL       BLOCK PRODUCTION ENABLED
delegate.nicocesar                 BTS6exFUYCieH6wYtbAxZLanncBqQH2po9XtPENfZr7otcASt5GFp           NO                    NO             0              N/A                     
nicocesar                          BTS7T4mdMCZH9X51MsfD7dH38CAEAFP7x3t76SkEK7LFUTtVPJQpR           2015-01-22T17:28:00   NO             1              N/A                     


then I did the registered:


bitsharewallet (unlocked) >>> wallet_account_register 
account_name: delegate.nicocesar
pay_from_account: nicocesar


Now I have it both registered but I thought that wallet_account_register will make it delegate .... but I don't see that


bitsharewallet (unlocked) >>> wallet_list_my_accounts                                     
NAME (* delegate)                  KEY                                                             REGISTERED            FAVORITE       APPROVAL       BLOCK PRODUCTION ENABLED
delegate.nicocesar                 BTS6exFUYCieH6wYtbAxZLanncBqQH2po9XtPENfZr7otcASt5GFp           2015-01-24T00:56:10   NO             0              N/A                     
nicocesar                          BTS7T4mdMCZH9X51MsfD7dH38CAEAFP7x3t76SkEK7LFUTtVPJQpR           2015-01-22T17:28:00   NO             1              N/A                 


How and I make it delegate?  did I screw up at some point

some extra info:

bitsharewallet (unlocked) >>> blockchain_get_block_count
1603646
bitsharewallet (unlocked) >>> blockchain_is_synced
true
bitsharewallet (unlocked) >>> wallet_account_balance nicocesar
No balances found.
bitsharewallet (unlocked) >>> wallet_account_balance delegate.nicocesar
No balances found.


Thanks in advance!

Quote from: onceuponatime on January 23, 2015, 07:12:32 AM

I'm not a tech guy, but I doubt that it is because you need to add nodes.

Maybe this will give you something to try?
https://bitsharestalk.org/index.php?topic=13606.msg177581#msg177581


If that is not it you should start a new thread here describing your problem and what you have done so far to get some tech help:
https://bitsharestalk.org/index.php?board=45.0

I deleted everything but the wallet then restarted the client and the same results. I'll do a git pull then recompile and try again. If it doesn't resolve the issue I'll just post a new thread


Again Thanks, onceuponatime for the bitshares and the patience !

Bien ahi Matute!

Nico Cesar

Quote from: onceuponatime on January 23, 2015, 01:27:44 AM
Sometimes when my client gets stuck at a block I try shutting it down and restarting. That usually gets the block count going again.

I did that several times

I added the seed nodes listed here
https://bitsharestalk.org/index.php?topic=5851.0

but block 1575645 is missing on my client

tell me if there is more seeds nodes to add that might have it. Thanks,



bitsharewallet (unlocked) >>> blockchain_get_block 1575644
{
  "previous": "0cf3b27d7a4848388fd189479a12b693772da92d",
  "block_num": 1575644,
  "timestamp": "2015-01-22T02:07:30",
  "transaction_digest": "c8cf12fe3180ed901a58a0697a522f1217de72d04529bd255627a4ad6164f0f0",
  "next_secret_hash": "12330aede6df7f2aaf588c4cf4d8a65f13ec2d28",
  "previous_secret": "04f1d4d7d0b8799fa017dd0cb043c77410eee73e",
  "delegate_signature": "200c4e4a4e99bc5f33b41cec8d0d7692383672ae0d677639826289144e0922fe9e58b64d37dc37d228cae7eaad7dcb553e98dac483793f22eac5abdfeb446dbdaa",
  "user_transaction_ids": [
    "208438f47c389337ab8bc8a0147e9de86d7ddd6f",
    "b02f288f37c739c26b8877bd3ff1cb0a77f3432b",
    "227e630686cf03084632341af1c57484630606bd",
    "491073d8486c00874a64720214889feef864c71f"
  ],
  "signee_shares_issued": 150000,
  "signee_fees_collected": 0,
  "signee_fees_destroyed": 150000,
  "random_seed": "93069645dafea22ffb11406928d818c80c06d97c",
  "block_size": 4206,
  "latency": 78161000000,
  "processing_time": 7585
}
bitsharewallet (unlocked) >>> blockchain_get_block 1575645
bitsharewallet (unlocked) >>>

So I see that my blockchain isn't up to date:



bitsharewallet (unlocked) >>> blockchain_get_block_count
1575644


(it took 30 minutes to go from 0 to that block ... then is stuck in there.

I see your generous donation later:
http://www.bitsharesblocks.com/blocks/block?id=1592918


how can I kick the blockchain process again?

Quote from: onceuponatime on January 22, 2015, 07:18:26 PM
Sent you funds to register  :)

I didn't get the shares...

I don't see my address in the blockchain:

bitsharewallet (unlocked) >>> blockchain_list_accounts nicocesar



bitsharewallet (unlocked) >>> wallet_account_balance nicocesar
No balances found.



bitsharewallet (unlocked) >>> wallet_list_accounts
NAME (* delegate)                  KEY                                                             REGISTERED            FAVORITE       APPROVAL       
delegate.nicocesar                 BTS6exFUYCieH6wYtbAxZLanncBqQH2po9XtPENfZr7otcASt5GFp           NO                    NO             0         
nicocesar                          BTS7T4mdMCZH9X51MsfD7dH38CAEAFP7x3t76SkEK7LFUTtVPJQpR           NO                    NO             1         
onceuponatime *                    BTS8Ae77UWtuXm71W8RsaF8yDhhxRme1ByiuEzWsprrB6mLzrmAYY           2014-07-19T03:18:40   NO             0         



bitsharewallet (unlocked) >>> wallet_get_account nicocesar
{
  "index": 11,
  "id": 0,
  "name": "nicocesar",
  "public_data": null,
  "owner_key": "BTS6X2niArKe1fGomYaAtghpWekoWFYqTJYRfgem7PmJujHRTTmE6",
  "active_key_history": [[
      "2015-01-22T17:19:05",
      "BTS7T4mdMCZH9X51MsfD7dH38CAEAFP7x3t76SkEK7LFUTtVPJQpR"
    ]
  ],
  "registration_date": "1970-01-01T00:00:00",
  "last_update": "2015-01-22T17:19:05",
  "delegate_info": null,
  "meta_data": null,
  "is_my_account": true,
  "approved": 1,
  "is_favorite": false,
  "block_production_enabled": false,
  "last_used_gen_sequence": 0,
  "private_data": null
}


but when I do:

bitsharewallet (unlocked) >>> wallet_get_account_public_address nicocesar
BTS1FfEXtaWvB3SRfG85cTZXNqCjog7Ssva


why a get a different address? what I'm doing wrong?

now active_key_history and wallet_list_my_accounts KEY column match:

I have:

nicocesar
BTS7T4mdMCZH9X51MsfD7dH38CAEAFP7x3t76SkEK7LFUTtVPJQpR

does that mean that I need to be beg funding?  *wink* *wink*

Thanks,
Nico

Quote from: wackou on January 22, 2015, 11:50:02 AM
well, that's because I have "nico" registered on the blockchain :D

:(  ....  lol ... I'll use another...

Quote from: wackou on January 22, 2015, 11:50:02 AM
"wallet_list_my_accounts" shows your account in your wallet, and "wallet_get_account" shows the one from the blockchain (which is mine) (the function name is a bit of a misnomer, there's also "blockchain_get_account" which is about the same, but seems to return the data in a different format)

Great! this SHOULD be part of the explanation on the delegates howto!... I'm  on it--

Quote from: wackou on January 22, 2015, 11:50:02 AM
This is strange as it should not have let you create the account with the name "nico" in your wallet knowing that there was already such an account on the blockchain (it's not a problem with the blockchain, but it can sometimes lead to confusion, as what just happened to you).

as I mention in another thread the issue was that I created the account *during* the sync of the blockchain ...  I'll start all over again and just wait for it to catch up-.

Thanks, "nico" ;)

Quote from: fluxer555 on January 22, 2015, 03:50:39 PM
Maybe you created the username before your blockchain finished syncing?

oooh.... That's correct. Mistery solved!

Why do I have 2 different address with   wallet_list_my_accounts and wallet_get_account  ?


bitsharewallet (unlocked) >>> wallet_list_my_accounts
NAME (* delegate)                  KEY                                                             REGISTERED            FAVORITE       APPROVAL       BLOCK PRODUCTION ENABLED
nico                               BTS4zxXSPKNwEDeJLHZaQNTGM3tKyYvsJdmXM9bXVKdTftfKuTbtP           NO                    NO             0              N/A                     
bitsharewallet (unlocked) >>> wallet_get_account nico
{
  "index": 12,
  "id": 11834,
  "name": "nico",
  "public_data": null,
  "owner_key": "BTS8WpBRYKRAY1P1i82PEwPA76e2wk3vXw6gtbjPFuVuasJVSJXZ9",
  "active_key_history": [[
      "2014-07-26T13:17:10",
      "BTS8WpBRYKRAY1P1i82PEwPA76e2wk3vXw6gtbjPFuVuasJVSJXZ9"
    ]
  ],
  "registration_date": "2014-07-26T13:17:10",
  "last_update": "2014-07-26T13:17:10",
  "delegate_info": null,
  "meta_data": null,
  "is_my_account": false,
  "approved": 0,
  "is_favorite": false,
  "block_production_enabled": false,
  "last_used_gen_sequence": 0,
  "private_data": null
}