Bitcoin Forum
November 01, 2024, 06:18:51 PM *
News: Bitcoin Pumpkin Carving Contest
 
   Home   Help Search Login Register More  
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 [22] 23 24 25 26 27 28 29 30 31 »
  Print  
Author Topic: Pebblecoin (XPB) - FIRST DPOS CRYPTONOTE COIN LIVE - Qt Wallet GUI - v0.4.4.1  (Read 56031 times)
This is a self-moderated topic. If you do not want to be moderated by the person who started this topic, create a new topic.
jwinterm
Legendary
*
Offline Offline

Activity: 3136
Merit: 1116



View Profile
April 21, 2015, 03:41:33 AM
 #421

Just downloaded latest binary and withdrew 1000 XPB from Poloniex to wallet address, and they're not showing up in my wallet. Poloniex says transaction is complete, with tx id  0ca0b0255f8d9026121d470bc68b5cc2337a1d7998d76e4dec79f192bd31a7d4 but I have zero balance in wallet using pebblecoind and simplewallet, both fully synced :/

Any suggestions on what to do? No block explorer?
XPB (OP)
Full Member
***
Offline Offline

Activity: 132
Merit: 100


View Profile
April 21, 2015, 04:10:09 AM
 #422

Just downloaded latest binary and withdrew 1000 XPB from Poloniex to wallet address, and they're not showing up in my wallet. Poloniex says transaction is complete, with tx id  0ca0b0255f8d9026121d470bc68b5cc2337a1d7998d76e4dec79f192bd31a7d4 but I have zero balance in wallet using pebblecoind and simplewallet, both fully synced :/

Any suggestions on what to do? No block explorer?
I think Poloniex is having some sync issues.  I wonder if they are on an alternative blockchain.  I don't see that tx from my node ("print_tx 0ca0b0255f8d9026121d470bc68b5cc2337a1d7998d76e4dec79f192bd31a7d4").  I'm currently communicating with them to update their daemon, hopefully once they do that and maybe resync it will work, though they shouldn't have had to update their daemon yet.  I will keep looking into this until it is resolved.
Mare76
Member
**
Offline Offline

Activity: 69
Merit: 10


View Profile WWW
April 21, 2015, 08:57:37 AM
 #423

Hi
Yesterday I sent some coins from my v0.3.0.2 client to the v0.4.1.2 and still nothing ...  Cry
Transaction ID: d73d7f6de5ec27751bf749ab4a21a8e33f114f55b88c21a5c99b3931e7f7d504
XPB (OP)
Full Member
***
Offline Offline

Activity: 132
Merit: 100


View Profile
April 21, 2015, 03:44:12 PM
Last edit: April 21, 2015, 04:03:08 PM by XPB
 #424

Hi
Yesterday I sent some coins from my v0.3.0.2 client to the v0.4.1.2 and still nothing ...  Cry
Transaction ID: d73d7f6de5ec27751bf749ab4a21a8e33f114f55b88c21a5c99b3931e7f7d504
Can you type
Code:
print_cn
into the command line window of your v0.3.0.2 wallet and paste what it shows you?

Also: is the transaction confirmed?

Finally: old wallets are compatible with new walletes.  So if you copy the 0.3.0.2 wallet and open it with the 0.4.1.2 client, and the coins aren't spent on the main network (which they don't appear to be), then you will still have access to them. 
XPB (OP)
Full Member
***
Offline Offline

Activity: 132
Merit: 100


View Profile
April 21, 2015, 04:13:05 PM
 #425

Hi
Yesterday I sent some coins from my v0.3.0.2 client to the v0.4.1.2 and still nothing ...  Cry
Transaction ID: d73d7f6de5ec27751bf749ab4a21a8e33f114f55b88c21a5c99b3931e7f7d504
Ok okay, I think I understand what is happening.  I changed the daemon's behavior to not relay transactions that are below the default fee.  However, I may have made a mistake and actually it doesn't accept them at all.  The old wallet by default has a fee that is too low.  So there are now two blockchains: the pre-fork one which contains transactions below the default fee, and the post-fork one which does not.

That was not intended, but now we have a forking change anyway (DPOS registration - with a new transaction type - has already started), so the answer is the same:  close your daemon/wallet, delete blockchain.bin from your data folder, and use the new daemon to re-sync.  Don't worry, you haven't lost any coins - the transactions spending them should be marked unconfirmed/invalid.

Meanwhile I'll work on a fix.
Mare76
Member
**
Offline Offline

Activity: 69
Merit: 10


View Profile WWW
April 21, 2015, 04:14:18 PM
 #426

 The RPC console is not implemented yet

and it is unconfirmed,  what can I do?
XPB (OP)
Full Member
***
Offline Offline

Activity: 132
Merit: 100


View Profile
April 21, 2015, 04:17:02 PM
 #427

The RPC console is not implemented yet
Yes, true.  I meant into the actual command prompt - the one with a black background - does that show up?

and it is unconfirmed,  what can I do?
Back-up the data, then just open it with the new qtwallet.  It should be compatible.  Then you can use the coins/send yourself the coins from there.
Mare76
Member
**
Offline Offline

Activity: 69
Merit: 10


View Profile WWW
April 21, 2015, 04:18:10 PM
 #428

Hi
Yesterday I sent some coins from my v0.3.0.2 client to the v0.4.1.2 and still nothing ...  Cry
Transaction ID: d73d7f6de5ec27751bf749ab4a21a8e33f114f55b88c21a5c99b3931e7f7d504
Ok okay, I think I understand what is happening.  I changed the daemon's behavior to not relay transactions that are below the default fee.  However, I may have made a mistake and actually it doesn't accept them at all.  The old wallet by default has a fee that is too low.  So there are now two blockchains: the pre-fork one which contains transactions below the default fee, and the post-fork one which does not.

That was not intended, but now we have a forking change anyway (DPOS registration - with a new transaction type - has already started), so the answer is the same:  close your daemon/wallet, delete blockchain.bin from your data folder, and use the new daemon to re-sync.  Don't worry, you haven't lost any coins - the transactions spending them should be marked unconfirmed/invalid.

Meanwhile I'll work on a fix.
I see, will try when I get home
Thanks
XPB (OP)
Full Member
***
Offline Offline

Activity: 132
Merit: 100


View Profile
April 21, 2015, 04:34:08 PM
 #429

Hi
Yesterday I sent some coins from my v0.3.0.2 client to the v0.4.1.2 and still nothing ...  Cry
Transaction ID: d73d7f6de5ec27751bf749ab4a21a8e33f114f55b88c21a5c99b3931e7f7d504
Ok okay, I think I understand what is happening.  I changed the daemon's behavior to not relay transactions that are below the default fee.  However, I may have made a mistake and actually it doesn't accept them at all.  The old wallet by default has a fee that is too low.  So there are now two blockchains: the pre-fork one which contains transactions below the default fee, and the post-fork one which does not.

That was not intended, but now we have a forking change anyway (DPOS registration - with a new transaction type - has already started), so the answer is the same:  close your daemon/wallet, delete blockchain.bin from your data folder, and use the new daemon to re-sync.  Don't worry, you haven't lost any coins - the transactions spending them should be marked unconfirmed/invalid.

Meanwhile I'll work on a fix.
I see, will try when I get home
Thanks
Right, and even easier:  you should not have to send yourself coins from 0.3.0.2 to 0.4.1.2 , the wallets are compatible.
XPB (OP)
Full Member
***
Offline Offline

Activity: 132
Merit: 100


View Profile
April 21, 2015, 05:57:15 PM
 #430

Congratulations to the first registered delegate!  This indicates the start of the forking change so everybody please update your daemons if you haven't already. 

To promote the coin and encourage people to become delegates, we've come up with an incentive scheme.

First, we'll send a free 100 XPB to anybody who PMs me their public address, for people to play around with and to start using the coin.

Second, once DPOS starts, for the first month of DPOS I'll send an extra 0.5 XPB to the signing delegate for every block they process.  This is on top of the usual transaction fees they will receive.  This is to encourage more people to become delegates at this important phase of the coin.
winston900
Newbie
*
Offline Offline

Activity: 21
Merit: 0


View Profile
April 21, 2015, 06:26:45 PM
 #431

as I do a transfer to poloniex in the new wallet.
XPB (OP)
Full Member
***
Offline Offline

Activity: 132
Merit: 100


View Profile
April 21, 2015, 06:39:21 PM
 #432

as I do a transfer to poloniex in the new wallet.
I apologize but I didn't get to putting the payment IDs in the new wallet.  I was working on the DPOS features.  I'll release a small update within a week which includes it.  Until then you have to keep using the simplewallet as before. 

But don't do it yet.  I don't think Poloniex has updated the daemon yet so they are out of sync with the network.
winston900
Newbie
*
Offline Offline

Activity: 21
Merit: 0


View Profile
April 21, 2015, 06:42:50 PM
 #433

as I do a transfer to poloniex in the new wallet.
I apologize but I didn't get to putting the payment IDs in the new wallet.  I was working on the DPOS features.  I'll release a small update within a week which includes it.  Until then you have to keep using the simplewallet as before. 

But don't do it yet.  I don't think Poloniex has updated the daemon yet so they are out of sync with the network.
yeah, right.
otherwise have tried using the simple old wallet and does not connect, will yah not available.
XPB (OP)
Full Member
***
Offline Offline

Activity: 132
Merit: 100


View Profile
April 21, 2015, 06:51:34 PM
 #434

as I do a transfer to poloniex in the new wallet.
I apologize but I didn't get to putting the payment IDs in the new wallet.  I was working on the DPOS features.  I'll release a small update within a week which includes it.  Until then you have to keep using the simplewallet as before. 

But don't do it yet.  I don't think Poloniex has updated the daemon yet so they are out of sync with the network.
yeah, right.
otherwise have tried using the simple old wallet and does not connect, will yah not available.
You have to use the new simplewallet with the new daemon.
winston900
Newbie
*
Offline Offline

Activity: 21
Merit: 0


View Profile
April 21, 2015, 06:55:30 PM
 #435

as I do a transfer to poloniex in the new wallet.
I apologize but I didn't get to putting the payment IDs in the new wallet.  I was working on the DPOS features.  I'll release a small update within a week which includes it.  Until then you have to keep using the simplewallet as before. 

But don't do it yet.  I don't think Poloniex has updated the daemon yet so they are out of sync with the network.
yeah, right.
otherwise have tried using the simple old wallet and does not connect, will yah not available.
You have to use the new simplewallet with the new daemon.

ok, I fix thanks for everything.
Kushedout
Legendary
*
Offline Offline

Activity: 1123
Merit: 1000


SaluS - (SLS)


View Profile
April 21, 2015, 10:05:40 PM
Last edit: April 21, 2015, 10:18:38 PM by Kushedout
 #436

Dear Ladies and Gentleman of the world,  I would like to make a nomination for your next DPoS Delegate, My Self. (Delegate ID# 21563)

If I am selected as your next trusted Delegate for your precious Pebblecoins (XPB), I promise to do my best to serve your coins by minting new stakes in timely fashion, with 24/7 uptime in order to ensure optimum security for the network and the health of blockhain as a whole.

My opponents will have you believe they are more qualified for this task and that they care for you by making empty promises.
I WILL NOT.

I come to you with experience, where my previous actions will speak loader than any words or promises made by my opponents.
I will let the fruits of my labor do all the talking.

So come this Friday, when it time for you, THE PEOPLE, to make the most critical decision of your life's, please cast your vote for me,
Kushed, as your next Delegate of 2015.  

God Bless America!!!

Vote Delegate ID# 21563

Thank you!

stoner19
Hero Member
*****
Offline Offline

Activity: 752
Merit: 500



View Profile
April 21, 2015, 10:12:02 PM
Last edit: April 21, 2015, 10:27:33 PM by stoner19
 #437

Dear Ladies and Gentleman of the world,  I would like to make a nomination for your next DPoS Delegate, My Self. (Delegate ID# 21563)

If I am selected as you next trusted Delegate for your precious Pebblecoins (XPB), I promised to do my best to serve your coins by minting new stakes in timely fashion, with 24/7 update in order to ensure optimum security for the network and the health of blockhain as a whole.

My opponents will have you believe they are more qualified for this task and that they care for you by making empty promises.
I WILL NOT.

I come to you with experience, where my previous actions will speak loader than any words or promises made by my opponents.
I will let the fruits of my labor do all the talking.

So come this Friday, when it time for you, THE PEOPLE, to make the most critical decision of your life's, please cast your vote for me,
Kushed, as your next Delegate of 2015.  

God Bless America!!!

Vote Delegate ID# 21563

Thank you!

I actually know kushed very well and without a doubt he has my vote. He's done well with organizing community staking pools for other coins, participated in some dev work, and is a very active community member/leader. Solid choice in my opinion.

Also, pick me too! #29140
Kevin77
Legendary
*
Offline Offline

Activity: 1652
Merit: 1057



View Profile
April 22, 2015, 08:45:55 AM
 #438

I tried to mine this and minerd crashes.
Still needs 13Gb RAM? Or do I need to have AES-NI?
vishwaratna
Member
**
Offline Offline

Activity: 70
Merit: 10


View Profile WWW
April 22, 2015, 11:00:58 AM
 #439

i want it free..

╲╲ ╲╲ COINOMAT.COM ▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬
╱╱ ╱╱ First Instant Crypto Exchange                              Sign Up Now!                    Visit our Facebook & Twitter
▃▃▃▃▃▃▃▃▃▃▃▃▃▃▃▃▃▃▃▃▃▃▃▃▃▃▃▃▃▃▃▃▃▃▃▃▃▃▃▃▃▃▃▃▃▃▃▃▃▃▃▃▃▃▃▃▃▃▃▃▃▃▃▃▃
XPB (OP)
Full Member
***
Offline Offline

Activity: 132
Merit: 100


View Profile
April 22, 2015, 03:51:34 PM
 #440

I tried to mine this and minerd crashes.
Still needs 13Gb RAM? Or do I need to have AES-NI?

You shouldn't need AES-NI.  It still needs 13 GB RAM though, the algorithm didn't change.
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 [22] 23 24 25 26 27 28 29 30 31 »
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!