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 - dxtr

Pages: 1 2 3 [4] 5
46
General Discussion / Re: Dry Run 7: The Power of DPOS
« on: July 02, 2014, 05:14:03 pm »
Code: [Select]
   TXN ID      SIZE          OPERATION COUNT          SIGNATURE COUNT
----------------------------------------------------------------------
  8b3495ae      9844                      102                      101
  ae3af881       340                        3                        2
  c8908453       244                        2                        1
  ce04af40       244                        2                        1
  d5c5e0e0       253                        3                        1
  dd3514a1       244                        2                        1
  f2242b6c       320                        3                        2
  f33fa096       340                        3                        2
  fac67bf9       320                        3                        2

When are those pending transactions being served?
I made some transfers between my accounts that are not registered (there was also one from registered -> unregistered), and those went into pending, and keep on hanging...

I thought that maybe only approved delegates validate them, but apparently they don't...

47
General Discussion / Re: Dry Run 7: The Power of DPOS
« on: July 02, 2014, 04:31:47 pm »
Quote from: vikram on July 02, 2014, 03:57:03 pm
Quote from: dxtr on July 02, 2014, 11:40:05 am
Quote from: cass on July 02, 2014, 10:54:18 am
Quote from: dxtr on July 02, 2014, 10:48:04 am
Does anyone know if keyhotee founders should have some initial funds after importing keyhotee id?

I did so, and have 0, maybe there is something one should do in order to receive it?

did you try

Code: [Select]
wallet_rescan_blockchain                                     

maybe this could help!?

I tried it, but not really :(
I'm afraid keyhotee funds are not included in this blockchain, but I'm not sure about that...

Do you get the funds if you import the private key for the PTS address which you used to donate as a Keyhotee Founder?

I will double check which key they are supposed to be associated with.

Thanks, I did import wallet.dat and it works fine, I got some XTS fromthere, not by wallet_import_keyhotee (as I thought I would get - my bad).


48
General Discussion / Re: Dry Run 7: The Power of DPOS
« on: July 02, 2014, 11:40:05 am »
Quote from: cass on July 02, 2014, 10:54:18 am
Quote from: dxtr on July 02, 2014, 10:48:04 am
Does(...)

did you try

Code: [Select]
wallet_rescan_blockchain                                     

maybe this could help!?

I tried it, but not really :(
I'm afraid keyhotee funds are not included in this blockchain, but I'm not sure about that...

49
General Discussion / Re: Dry Run 7: The Power of DPOS
« on: July 02, 2014, 10:48:04 am »
Does anyone know if keyhotee founders should have some initial funds after importing keyhotee id?

I did so, and have 0, maybe there is something one should do in order to receive it?

50
General Discussion / Re: Dry Run 7: The Power of DPOS
« on: July 02, 2014, 10:40:50 am »
Guys if you thing scroodge is a trustworthy delegate, then please
wallet_approve_delegate scroodge true
or send some funds here:
scroodge                           XTS67u5mjusU3XXna7EmqyeGedMwREEUYKg7k5g6GeFTLqyLBEify

I'm out of circulation on 103rd position right now :(

51
General Discussion / Re: Dry Run 7: The Power of DPOS
« on: July 02, 2014, 09:51:56 am »
May I ask if you guys are planning to add some functionality that's allowing automatic payouts from a delegate to a configurable account after defined threshold is crossed?

52
General Discussion / Re: Dry Run 7: The Power of DPOS
« on: July 02, 2014, 06:56:41 am »
Can I have some funds to start my delegate?

(I read about export to json too late)


scroodge                           XTS67u5mjusU3XXna7EmqyeGedMwREEUYKg7k5g6GeFTLqyLBEify

Thx a lot!

53
General Discussion / Re: Dry Run 6: Great Scott!
« on: July 01, 2014, 08:32:25 am »
It was sufficient to update to latest codebase to get delegate going.
I misunderstood when the new dry run was going to start.

54
General Discussion / Re: Dry Run 6: Great Scott!
« on: July 01, 2014, 04:53:58 am »
Guys, please, vote me back in,

I probably got voted out, don't know why, but since half of delegates are doubles/inits this doesn't sound fare.

I want to participate in the next run.

55
General Discussion / Re: Dry Run 6: Great Scott!
« on: June 30, 2014, 06:38:00 pm »
Quote from: liondani on June 30, 2014, 06:10:29 pm
I have two accounts also...
 
one liondani (delegate registered)
and liondaniel (non delegate registered)

I have made before 2 days a succesfull transaction between them...
Now I tried to sent 400 XTS from liondaniel to liondani but after I gave the password nothing happens!
I closed the client and tried again (I checked the balances, no change) and then I waited about 5 minutes after I gave the password  and then the client informed me about the "pending transaction"

l

Code: [Select]
liondaniel (locked) >>> wallet_transfer 400 XTS liondaniel liondani
passphrase:

IOK
    BLK.TRX  TIMESTAMP           FROM                TO                  MEMO                                             AMOUNT             FEE              ID
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
   pending   2014-06-30T18:02:11 liondaniel          liondani                                                      400.00000 XTS         0.10000 XTS        50f902e5

Disable delegate, rescan from block 2100, enable delegate, check if transaction is fine on your wallet (it's on main chain in block 2109, from what I see)

If this doesn't help,
- backup your prv keys,
- wipe .BitSharesXTS folder,
- update to latest codebase from git,
- create wallets and import backed-up keys,
- then rescan blockchain,
and you should be fine.

56
General Discussion / Re: Dry Run 6: Great Scott!
« on: June 30, 2014, 05:38:05 pm »
I have two wallets, one is regular, second is a delegate.
When I perform transfers between those two wallets I get wallet_account_transaction_history behaving strange on those two wallets,
on one I can see FROM and TO as UNKNOWN and AMOUNT = 0,
on the other all fields are filled just fine.

I send XTS between two registered accounts.


----------------------------------------------------------------------------------------------------------------------------------------------------------------
    364.0    2014-06-26T11:02:00 dxtr                scroodge            10.00000 XTS        0.00000 XTS         test                                   b5c137d1
    372.0    2014-06-26T11:30:00 dxtr                scroodge            1.00000 XTS         0.00000 XTS         test3                                  cd2fb06c
    903.0    2014-06-27T17:44:00 UNKNOWN             UNKNOWN             0.00000 XTS         0.00000 XTS                                                c4a7358c
    913.0    2014-06-27T18:12:00 XTS868i824vqDYu6... scroodge            2.00000 XTS         0.00000 XTS                                                d8bfd123
    914.0    2014-06-27T18:14:00 UNKNOWN             UNKNOWN             0.00000 XTS         0.00000 XTS                                                58e12110
    982.521  2014-06-27T21:50:00 dxtr                scroodge            40.00000 XTS        0.00000 XTS                                                c6f54cfa
    990.184  2014-06-27T22:18:00 UNKNOWN             UNKNOWN             0.00000 XTS         0.00000 XTS                                                46281c2d
   1180.0    2014-06-28T08:42:00 UNKNOWN             UNKNOWN             0.00000 XTS         0.00000 XTS                                                00679a13
   1180.554  2014-06-28T08:42:00 UNKNOWN             UNKNOWN             0.00000 XTS         0.00000 XTS                                                e0cc86e8
   1703.0    2014-06-29T18:54:19 scroodge            dxtr                10.40000 XTS        0.10000 XTS                                                38916066
scroodge-wallet (unlocked) >>> wallet_open dxtr-wallet
OK
dxtr-wallet (locked) >>> wallet_account_transaction_history scroodge
    BLK.TRX  TIMESTAMP           FROM                TO                  AMOUNT              FEE                 MEMO                                   ID     
----------------------------------------------------------------------------------------------------------------------------------------------------------------
    914.0    2014-06-27T18:14:00 scroodge            dxtr                2.00000 XTS         0.00000 XTS                                                58e12110
    990.184  2014-06-27T22:18:00 scroodge            dxtr                10.00000 XTS        0.00000 XTS                                                46281c2d
   1180.554  2014-06-28T08:42:00 scroodge            dxtr                10.00000 XTS        0.00000 XTS                                                e0cc86e8
   1180.0    2014-06-28T08:42:00 scroodge            dxtr                10.00000 XTS        0.00000 XTS                                                00679a13
   1703.0    2014-06-29T18:58:00 scroodge            dxtr                10.40000 XTS        0.00000 XTS                                                38916066


Why is it so?

57
General Discussion / Re: Dry Run 6: Great Scott!
« on: June 30, 2014, 02:32:27 pm »
Please, can I get some XTS so I can put my delegate a few spots higher?

Public key:XTS6hjYfVGrPDFKQc5oLTVp5rU56m15XnEvVCtzMLkyDMni2rentc
Account name: dxtr


Also, when are delegates' funds supposed to be available for them to spend? After every round is over or some other moment?

Thanks.

58
General Discussion / Re: Dry Run 6: Great Scott!
« on: June 27, 2014, 08:21:28 am »
Guess I pulled too early...


dev_fixture.hpp:226:80: error: ‘class bts::client::client’ has no member named ‘get_next_producible_block_timestamp’


Is there a solution for this?


59
General Discussion / Re: [new DAC] Satoshi Fantasy - Fantasybits
« on: June 26, 2014, 10:09:34 pm »
So it all comes down to a consensus of how a value is being created - if you create an algorithm that rewards majority of people just by honestly following a "decalog" for what is meaningful for them, then you have a succesfull DAC attracting beliefs driven people.

60
General Discussion / Re: Dry Run 6: Great Scott!
« on: June 26, 2014, 02:17:59 pm »
I have 2 strange cases:
1)

dxtr-wallet (unlocked) >>> blockchain_list_blocks 409 3
    HEIGHT                          TIME      TXN COUNT                                                 SIGNING DELEGATE    SIZE LATENCY
----------------------------------------------------------------------------------------------------------------------------------------
       409           2014-06-26T13:28:00              2                                                         scroodge     584       
       410           2014-06-26T13:30:00              1                                                  delegate-dorian     499       1
       411           2014-06-26T13:32:00              0                                                          vikram9     182      25
dxtr-wallet (unlocked) >>> blockchain_get_delegate_block_stats vikram9
[[
    231,{
      "missed": false,
      "latency": null
    }
  ],[
    356,{
      "missed": false,
      "latency": null
    }
  ],[
    411,{
      "missed": false,
      "latency": 25
    }
  ]
]
dxtr-wallet (unlocked) >>> blockchain_get_delegate_block_stats scroodge
[[
    411,{
      "missed": false,
      "latency": 0
    }
  ]
]


One command, blockchain_get_delegate_block_stats says that both scroodge and vikram9 have produced the same block,
another command, blockchain_list_blocks 409 3 lists that block 409 was created by scroodge, not 411.

2) When I send some XTS from one and the same wallet account to another in this same wallet, transaction is processed, but XTS disappears from source and does not appear in target (one of accounts is a delegate, so there is no blockchain rescan afterwards [I think]).

Are those known issues?


Pages: 1 2 3 [4] 5

Page created in 0.211 seconds with 24 queries.