 Show Posts
|
|
Pages: « 1 [2] 3 4 5 6 »
|
Please update to new wallet and stake. |
|
|
|
|
Source and windows wallet with checkpoints on OP
Mac will be done soon.
Please update and stake on new wallet so the new
fork prevails.
|
|
|
|
|
compiling new wallets with checkpoints
but we do need some staking wallets
on the new fork.
|
|
|
|
I had 2 payments for my 3 MN's. But what guess what, both of them orphaned or whatever... Status: conflicted
Date: 27.4.2015 02:10
Source: Generated
Credit: 0.88 8BIT
Net amount: 0.00 8BIT
Transaction ID: 9dc3ddb91b3323fcd635c29613abfe552ea73c3f90e4781f8864a1f9efb38124-000
Generated coins must mature 251 blocks before they can be spent. When you generated this block, it was broadcast to the network to be added to the block chain. If it fails to get into the chain, its state will change to "not accepted" and it won't be spendable. This may occasionally happen if another node generates a block within a few seconds of yours.
Please confirm if you are getting these aswell. I see some old wallets still staking. working on adding a block on the hardcoded node. |
|
|
|
|
Fork is a success, you should be getting your node payments now @ 0.88 8BIT
Next we move on to enable anon and add fees to anon TX that will go to MN's.
Please report any issues you might go through after the fork so I can look into
it, if any comes up.
|
|
|
|
|
About 70 blocks left to fork @ block 11500.
Please insure your wallet is up to date.
The old wallet will not accept blocks after 11500
Bittrex and Cryptsy have confirmed updated wallets,
Please check with other exchanges before sending
or withdrawing 8BIT.
|
|
|
|
|
Bittrex updated yesterday, Cryptsy in the process.
I will check with other exchanges as well.
|
|
|
|
200 blocks left
I see 464 left. fork will occur at block 11500. |
|
|
|
548 blocks left.
Even tho 3 of my masternodes are configured stake=0, I have stacked with all of them. However, I had a lot of orphaned ones. :/
You did not stake, what you see is node payments from the current PoS blocks. Also you did not orphan anything, orphan blocks will show when someone on the network gets one. Status: conflicted
Date: 26.4.2015 05:35
Source: Generated
Credit: 0.00787056 8BIT
Net amount: 0.00 8BIT
Transaction ID: 12dd0c0b3256a24352b5af8185850eeb77c3441d69c843d87f7dcff8819ea9b6-000 Hmm what are these than, I have loads of them.  That's a node payment of 0.00787056 8BIT, after block 11500 it will be fixed at 0.88 8BIT The PoS block originated at another address. Also you might want to do repairwallet in console it seems you have some conflicted TX. I did repairwallet and got: {
"wallet check passed" : true
}I guess it should be okay now? Yes, it might been resolved already. |
|
|
|
548 blocks left.
Even tho 3 of my masternodes are configured stake=0, I have stacked with all of them. However, I had a lot of orphaned ones. :/
You did not stake, what you see is node payments from the current PoS blocks. Also you did not orphan anything, orphan blocks will show when someone on the network gets one. Status: conflicted
Date: 26.4.2015 05:35
Source: Generated
Credit: 0.00787056 8BIT
Net amount: 0.00 8BIT
Transaction ID: 12dd0c0b3256a24352b5af8185850eeb77c3441d69c843d87f7dcff8819ea9b6-000 Hmm what are these than, I have loads of them. That's a node payment of 0.00787056 8BIT, after block 11500 it will be fixed at 0.88 8BIT The PoS block originated at another address. Also you might want to do repairwallet in console it seems you have some conflicted TX. |
|
|
|
548 blocks left.
Even tho 3 of my masternodes are configured stake=0, I have stacked with all of them. However, I had a lot of orphaned ones. :/
You did not stake, what you see is node payments from the current PoS blocks. Also you did not orphan anything, orphan blocks will show when someone on the network gets one. |
|
|
|
Earlier someone said that a MN with the internal ip address 192.168.1.128 will not work. I am curious how this happened, how it can be fixed, and what will happen if it is not fixed.
You need to find your external IP and replace that 192.168.x.x in the conf file. What will happen: the node with the internal IP will be kicked out from list. To find your external IP search google for " What is my IP " |
|
|
|
* You can send to and receive coins from exchanges, however, after block 11500
you need to make sure the exchange updated the wallet
you are not going to ask them to update? you need to send bittrex and the other exchanges a support ticket as the developer. All exchanges have been informed, but some take longer to update. I will mark exchanges that confirm update on OP. At this time there is nothing to worry about. when we get close to block 11500 make sure you use exchanges that confirmed the update. |
|
|
|
|
I skipped through the pages since I crashed last night. " I needed some rest "
here is a few things you should know:
If your IP address is not static it will still work with your dynamic address until it changes,
if it does change then you can change it in the conf file and it will work again.
Use coin control to make sure your 112 coins in your node address are not used while
sending coins before the node is up. if your node is up the 112 coins will not be available
to send and break the node. When receiving coins use a different address in the wallet.
The payments coming in now are a percent of the 8% yearly PoS and sometimes
will be very small until block 11500 at which point they will be fixed.
The wallet needs time to connect with all the Masternodes so seeing different lists
in different wallets is normal, eventually if left running all wallets will connect.
Incorrectly configured node will appear in the list but will be kicked out when
it fails verification. Your node will take 5 to 10 minutes to appear in node list.
Your external IP address for conf file can be found by typing this in google search
" What is my IP "
A few community members are helping, I would like to thank everyone who
does. Please ask your questions in the thread, I still have the 360 seconds limitation
and can not answer PM's quickly.
There is no such thing as a "stupid" question, try to get your answer in the thread,
so everyone can see that answer.
I need to clear my head and move on to stage 4, but will be around to help and
make sure the fork is smooth at block 11500.
* You can send to and receive coins from exchanges, however, after block 11500
you need to make sure the exchange updated the wallet
|
|
|
|
|
I need to go eat dinner and get a little rest before I miss all my meals for the day.
I will come back to answer any questions that come up, but there is plenty of people
around to help.
Do not rush, you still have about two days before HiPoS payments
start to make your MN's.
Exchanges have been informed. Tomorrow I will make more detailed
guides on how to run MN's and multiple MN's
|
|
|
|
Little help please. I am getting "not capable masternode: Could not connect to 173.29.34.95:9999" any help?
Open Port 9999 in your router. search google on how to do that for your router model. |
|
|
|
How do we check if our masternode is working?
After a successful Masternode start, wait 5 minutes and look for your IP address in the Masternode Tab list. Note: Make sure you use your external IP address, not local. You can check that by typing " What is my IP " in google search |
|
|
|
any help on where Im going wrong pls dev, followed the guide and get the error "invalid masternodepriv key" when trying to load up the wallet after generating the masternode priv key
Could be a typo or a spacing. You can try generating the key again. Double check the steps you used and make sure you enter correct values in the conf file where it's needed. |
|
|
|
Simple guide on how to create a masternode:
Start your 8BIT wallet
Send exactly 112 8BITS to an address in your wallet
Go to Help/Debug/Console
type the following and hit Enter:
Copy the result and place that in the 8bit.conf file below:
rpcallowip=127.0.0.1
rpcuser=YourUserName
rpcpassword=YourRPCPassword
rpcport=any_valid_port EX: 9228
server=1
daemon=1
listen=1
staking=0
port=9999
masternodeaddr=YOUR_IP:9999
masternode=1
masternodeprivkey=KEY GENERATED BY COMMAND masternode genkey
Port 9999 must be open.
Restart your wallet and go back to Help/Debug/Console
Type the following and hit enter:
* Give your Masternode a few minutes, and check if it's up in the Masternode list how to create multiple masternodes in the same wallet? You need to run multiple instances of the wallet with different ports. |
|
|
|
|
