Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - djdexter

Pages: [1]
1
Stakeholder Proposals / Re: Candidate Billboards
« on: June 16, 2014, 09:42:03 pm »
Physical machine:
8 GB RAM
Intel I3 (last gen)
WD Black (stripe)
UPS

I can spin aditional Virtual Machines if this physical machine is not enough.

What i will offer:

-Redundant Backups
-Reserved Timeslot for updating the codebase (if needed)
-Dumping logs (for developers)
-pro bono SLA ( Service Level Agreement ) based support for urgent matters at given time frame for bitshares source
-Bitshares software monitoring log parsing / alert system at my nodes
-Stable internet  connection DSL (15/15 Mbps)

Delegates Addresses : TBA (when there will be at least more stable version)


2
General Discussion / Re: Dry Run 2: The Real Deal
« on: June 13, 2014, 02:40:41 pm »
Hi Bytemaster,

djdexter (unlocked) >>> blockchain_get_config
{
  "blockchain_id": "964b38343dc7337f8d87a16323faaa7c63b95160c73739c6d0a276ef41f37312",

It seems i'm on different chain .

How can i fix this ? i tried git pull / recompile  / and deleted ~/.BitSharesXTS.


djdexter (unlocked) >>> addnode "95.85.33.16:8764" "add"
OK
--- there are now 0 active connections to the p2p network

After 2 mins i tried

djdexter (unlocked) >>> bitcoin_getconnectioncount
0

I'm getting no connections on network , but i can ping that addr

djdexter@ficko:~/bitshares_toolkit/programs/client$ ping 95.85.33.16
PING 95.85.33.16 (95.85.33.16) 56(84) bytes of data.
64 bytes from 95.85.33.16: icmp_seq=1 ttl=55 time=45.8 ms



You mean to delete ~/.BitSharesXTS folder by "data-dir" ?

Yes, ~/.BitSharesXTS is the data-dir. It is strange, try do launch this command:

Quote
addnode "95.85.33.16:8764" "add"

Run this command to make sure you are on the same chain ID.
Quote
blockchain_get_config
{
  "blockchain_id": "ba0309904a7b0a2fb4c4c0f5796ca97eb8366726b491204434f918dc3349f843",

3
General Discussion / Re: Dry Run 2: The Real Deal
« on: June 13, 2014, 02:36:08 pm »
djdexter (unlocked) >>> addnode "95.85.33.16:8764" "add"
OK
--- there are now 0 active connections to the p2p network

After 2 mins i tried

djdexter (unlocked) >>> bitcoin_getconnectioncount
0

I'm getting no connections on network , but i can ping that addr

djdexter@ficko:~/bitshares_toolkit/programs/client$ ping 95.85.33.16
PING 95.85.33.16 (95.85.33.16) 56(84) bytes of data.
64 bytes from 95.85.33.16: icmp_seq=1 ttl=55 time=45.8 ms



You mean to delete ~/.BitSharesXTS folder by "data-dir" ?

Yes, ~/.BitSharesXTS is the data-dir. It is strange, try do launch this command:

Quote
addnode "95.85.33.16:8764" "add"

4
General Discussion / Re: Dry Run 2: The Real Deal
« on: June 13, 2014, 02:14:51 pm »
You mean to delete ~/.BitSharesXTS folder by "data-dir" ?

i did that 2 hours ago and made git pull and recompiled the code


Here is my blockchain head info:

  "blockchain_head_block_num": 6416,
  "blockchain_head_block_time": "20140612T073600",

I think you are in an old fork, this is my state:
Quote
"blockchain_head_block_num": 1431,
"blockchain_head_block_time": "20140613T135645",

Try to recompile, erase your data-dir and relunch

5
General Discussion / Re: Dry Run 2: The Real Deal
« on: June 13, 2014, 01:39:44 pm »
Dear all ,

Can someone also explain me this situation?

My delegate is marked as inactive, and i'm running bitshares_client in background all day ?

** Inactive:
301         djdexter-1               3000000             0                   2.99997e-05 %       0               0

Should i do anything ? Or this is normal?

Here is my blockchain head info:

  "blockchain_head_block_num": 6416,
  "blockchain_head_block_time": "20140612T073600",



6
General Discussion / Re: Dry Run 2: The Real Deal
« on: June 13, 2014, 01:35:27 pm »
I have one question.

I have latest build (pulled one hour ago from this post time)

I'm seeing following value:
 "blocks_produced": 0

But i see
"last_block_num_produced": 4294967295


So it basically says that there is at least one block produced with following number "4294967295", but it does not count this block on blocks_produced placeholder.



Can someone explain this to me ?

Quote
djdexter (unlocked) >>> wallet_get_account djdexter-1
{
  "index": 4,
  "id": 301,
  "name": "djdexter-1",
  "public_data": null,
  "owner_key": "XTS61oES21C3VkpczAoAZEBWCEF2bPdBGwPSfBupyN34LKmF79y5Y",
  "active_key_history": [[
      "20140610T232300",
      "XTS61oES21C3VkpczAoAZEBWCEF2bPdBGwPSfBupyN34LKmF79y5Y"
    ]
  ],
  "delegate_info": {
    "votes_for": 3000000,
    "votes_against": 0,
    "blocks_produced": 0,
    "blocks_missed": 0,
    "pay_balance": 0,
    "next_secret_hash": "0000000000000000000000000000000000000000",
    "last_block_num_produced": 4294967295
  },
  "registration_date": "20140610T232300",
  "last_update": "20140610T232300",
  "meta_data": null,
  "account_address": "XTSFhKaGFphYT6avaCFWpTVGRVSGhw9r9Pxh",
  "trust_level": 0,
  "private_data": null
}

4294967295 is the maximum value for an unsigned (never negative) 32 bit integer, and is not an actual block number that has been created in the chain.  Basically it says that because it was never changed to something legitimate, because you never produced a block.

Actually i did not thought about the numeric value :)

You are absolutely right !

Thanks for the info  +5%

7
General Discussion / Re: Dry Run 2: The Real Deal
« on: June 13, 2014, 12:32:59 pm »
I have one question.

I have latest build (pulled one hour ago from this post time)

I'm seeing following value:
 "blocks_produced": 0

But i see
"last_block_num_produced": 4294967295


So it basically says that there is at least one block produced with following number "4294967295", but it does not count this block on blocks_produced placeholder.



Can someone explain this to me ?

Quote
djdexter (unlocked) >>> wallet_get_account djdexter-1
{
  "index": 4,
  "id": 301,
  "name": "djdexter-1",
  "public_data": null,
  "owner_key": "XTS61oES21C3VkpczAoAZEBWCEF2bPdBGwPSfBupyN34LKmF79y5Y",
  "active_key_history": [[
      "20140610T232300",
      "XTS61oES21C3VkpczAoAZEBWCEF2bPdBGwPSfBupyN34LKmF79y5Y"
    ]
  ],
  "delegate_info": {
    "votes_for": 3000000,
    "votes_against": 0,
    "blocks_produced": 0,
    "blocks_missed": 0,
    "pay_balance": 0,
    "next_secret_hash": "0000000000000000000000000000000000000000",
    "last_block_num_produced": 4294967295
  },
  "registration_date": "20140610T232300",
  "last_update": "20140610T232300",
  "meta_data": null,
  "account_address": "XTSFhKaGFphYT6avaCFWpTVGRVSGhw9r9Pxh",
  "trust_level": 0,
  "private_data": null
}

8
General Discussion / Re: Dry Run 2: The Real Deal
« on: June 13, 2014, 12:21:39 pm »
Info:
djdexter-1 *                       XTS61oES21C3VkpczAoAZEBWCEF2bPdBGwPSfBupyN34LKmF79y5Y           2014-06-10T23:23:00   0

Physical machine:
Intel i3 (last gen)
8 GB rm
Stable DSL(15 Mbps up/down)
UPS backup
Regular backups / maintenance (system administration)

Virtual machine (only one running)
OS: Ubuntu 14.04
Bitshares_toolkit

-Development/IT background
-Log analysis
-Debugging
-OBDR restore procedures ( one button disaster recovery )


If needed in future i can spin more machines on dedicated systems or cloud.


9
Can someone share screenshot of the Qt GUI?
I'm interested in it but i'm not OS X user :/

10
General Discussion / Re: BitShares X Status Update
« on: January 21, 2014, 10:27:18 pm »
What a good status updates from development team !!

I finally get compiled wallet on ubuntu.

Can someone send me some test bitshares on my address GRukroLpAKRgPAQcmsbY4EKJaMM ?




Pages: [1]