Hopefully this hasn't been asked many times before but I set up my masternode today and it's been over 4 hours (around 7 hours) and haven't been paid yet
I checked the masternode list and my ip is listed as well. The masternode is also enabled in the wallet and wallet is unlocked.
Just wondering how long it takes to receive that first payment.
Thanks in advance
When you set up a new masternode, it takes a while for it to be fully registered across the network. You may need to wait a day or 2 until this happens, then the rewards will start coming regularly |
|
|
|
This is just an orphaned block. If two blocks compete on the same height one of them will be marked as invalid by the block chain. They are usually (at least by most cryptocurrencies) marked with -1 confirmations when this happens. These collisions can happen at any time when two blocks are generated at a close-by time to each other and submitted on the same height. However, there can only be one valid block. The block chain decides which one it considers the correct one. The new currency generated in the invalid block will not be accepted onto the block chain. Yours, team swipp Understood. Is it strange then that, for the 2 addresses that received coins in the orphaned block, the explorer shows these 2 address as having received the coins? I ask as I thought my troublesome masternode had received a reward, but the reward is from the orphaned block. It doesn't appear in the node's wallet if I 'listtransactions' but does appear in the explorer. http://explorer.swippcoin.com/address/SWzBtL4ntuUj4CiBWb6CE5Vda5TKK4g14H |
|
|
|
I'm one of those with "unknown issue, this one has us stumped". Any info you can share? I guess I will need to set it up somewhere else, try a fresh start on a new server.
We noticed we can connect to the port and that we are not being thrown out. Other than that, it's really hard to tell. Sometimes you can get a clue on the side that tries to send a payment to a masternode (by looking in the debug.log), but in this case, it's pretty difficult to know what's going on. How is your swipp.conf set up ? Yours, team swipp I can simplify the conversation. I've been running 2 SWP masternodes. They're set up the same way (the only difference is that they're on different VPS providers) and up until 140,000 they've been running fine. Once 140,000 hit, one masternode kept receiving rewards but the other stopped. I couldn't find an obvious reason why. I've recently moved the non-functioning masternode to a VPS from the same provider as for the masternode that does still work. I'm waiting now to see if it will start receiving rewards once it's fully registered on the network. This is essentially as close as I can get to having both masternodes be the same. I won't know what else to do if this doesn't solve the problem. It also makes me a bit wary about my thoughts of moving a masternode to a less crowded IP location to avoid reduced rewards. Seems risky now, assuming I can get this masternode functioning again. This might not have anything to do with it, but I've also found several RPC commands have never worked properly, i.e.: 'masternode winners' returns nothing. Might just be the ugly codebase you guys inherited. |
|
|
|
I'm one of those with "unknown issue, this one has us stumped". Any info you can share? I guess I will need to set it up somewhere else, try a fresh start on a new server.
We noticed we can connect to the port and that we are not being thrown out. Other than that, it's really hard to tell. Sometimes you can get a clue on the side that tries to send a payment to a masternode (by looking in the debug.log), but in this case, it's pretty difficult to know what's going on. How is your swipp.conf set up ? Yours, team swipp I can simplify the conversation. I've been running 2 SWP masternodes. They're set up the same way (the only difference is that they're on different VPS providers) and up until 140,000 they've been running fine. Once 140,000 hit, one masternode kept receiving rewards but the other stopped. I couldn't find an obvious reason why. I've recently moved the non-functioning masternode to a VPS from the same provider as for the masternode that does still work. I'm waiting now to see if it will start receiving rewards once it's fully registered on the network. This is essentially as close as I can get to having both masternodes be the same. I won't know what else to do if this doesn't solve the problem. It also makes me a bit wary about my thoughts of moving a masternode to a less crowded IP location to avoid reduced rewards. Seems risky now, assuming I can get this masternode functioning again. |
|
|
|
strangely, my MN always worked and received a rewards. But suddenly after 140,000 became a "firewall closed, rejecting connections"  How is this possible?  Good question. I can pretty much guarantee nothing related to this has changed in the wallet though. Some firewalls will close a port only after an application restarts. It's definitely either the firewall or miss-configured port though, because there is nothing on the other side to handle the connection. Yours, team swipp I can appreciated that it's a mystery for both parties. Nothing has changed in the masternode code and nothing has changed in the masternodes we're running, but there is this problem of no rewards. Hopefully we're all able to get to the bottom of it somehow. I'll keep experimenting. |
|
|
|
Hello everybody!
We have been working with the pool operator for our biggest pool (lpool) to fix the issue with the masternode payments. We can report that it is now working properly and that the first masternodes have now received rewards;
http://explorer.swippcoin.com/tx/0542a3557efd92e0a360f591bc6dbef8b5b2057b3e4d3ddee0f47776dfcf55f0
http://explorer.swippcoin.com/tx/802b48b8c58db29831f345e46b9e32bae0625652bffbd3219a15c5838ac02743
http://explorer.swippcoin.com/tx/ed27c41fbf0e31819aa0b2fffd6c43488cb87525889d64a8ee2e277ac0070021
Thanks to lpool for helping out and assisting us to work out this issue  .
We will also contact the operator for Altcoinix and get it sorted there as well. Once this is done, we can enforce the payments in the block chain!
We can also report that all masternodes have started to receive payments except these ones;ScWVC1uMD1QndgC1Y2SukFMUqLf9SGZTuf (firewall closed, rejecting connections)
SMaQo9DtZ42xCfLwDCfHjXAuE2aE1G6Hh1 (connects, but then instantly drops our connection)
SgNw1v7nxNEgUUwUThpsirfADgRDLx2vhL (unknown issue, we recommend changing port to 24055)
SbJkMr56p1jrNyw2bE4pouXisqqAVzaQ8k (connects, but then instantly drops our connection)
SToJDfws4nLMXHz1EKB9GssK5kuEmiUzTM (firewall closed, rejecting connections)
SjE9MpK8Kk17RhNpnZEjdwH7aSHFicajJJ (firewall closed, rejecting connections)
SiPsK8tSQPU8dfvqW38QxGDKTdkCBDXrRy (unknown issue, this one has us stumped)
SWzBtL4ntuUj4CiBWb6CE5Vda5TKK4g14H (unknown issue, this one has us stumped)
SQD4ByPU9UDrs1bXYDZKFTcqNxU67ycarS (firewall closed, rejecting connections)
SVM1NsL9L383tJX2VDKEQVPxny16uLLVL8 (firewall closed, rejecting connections)
SPgewyvbgCvY8Qz3wmQbvBLcq1rXNgJQqW (firewall closed, rejecting connections)
If we were able to identify the problem, we have listed it above. As you can se, most of them have a valid explanation. Currently, we have 11 masternodes misbehaving in one way or another. If it's incorrectly set up, you will obviously not receive payments.
If you are on that list with "unknown issue" and manage to work out what is causing your problems, please let everybody in the thread know.
Yours, team swipp I'm one of those with "unknown issue, this one has us stumped". Any info you can share? I guess I will need to set it up somewhere else, try a fresh start on a new server. |
|
|
|
Why only 10 out of 25 working masternodes receive a reward? Check in the explorer - many nodes do not get the reward after 140,000 blocks.
Since yesterday, awards for masternodes have ceased. I put my masternode again from the very beginning with a new address, but I have not received a single award. But at the same time my masternode is working.
v.2.1.0.0 Yggdrasil
Windows 7
I can confirm this. After 140,000 my masternode stopped receiving any rewards. I also tried to fix this by starting again from scratch with a new address but, so far, it has not made any difference. Rewards have simply stopped. |
|
|
|
OK. So after block 140 000 it looks like our two main pools are simply throwing part of the PoW reward away. Luckily, at this stage, we are just validating the sums in the transactions, so these are the ones that are being generated in each PoW block;
12 * 0.6 = 7.2 Swipp (going to the miner)
12 * 0.4 = 4.8 Swipp (going to the masternode)
It seems the second transaction/sum is being ignored and just thrown away by both pools. We are only validating that the sums match, so according to the chain, this is completely fine. We actually did it this way because we anticipated that something like this might happen... Exclusively requiring the masternode payment would instead completely invalidate the block - which would be an even bigger problem. However, the next step is to always require it.
We are investigating. We will work with one of the pool operators to fix this issue as painlessly as possible!
Yours, team swipp
When you say "throwing part of the PoW away" you mean these coins were generated and essentially burnt? Or they were never actually generated? |
|
|
|
Hello everybody. We are now approaching block 140 000 and should be hitting it some time today! Hopefully, the transition will go without any hitches and everything behaves as it did on the testnet during testing.
We have informed our two main pools (lpool and altcoinix) about the upgraded wallet. We can confirm that they have both switched to the new version - so there should be no issues to keep up mining.
Our current exchange (coinsmarkets.com) was also informed some time ago about the update. They have also switched to the new Yggdrassil wallet.
The build instructions on the GitHub page have been updated. The current version of the source code also has a script for cross compiling a Windows binary. We also have a testing script that can be used to set up a local Swipp testnet for testing purposes. We will cover these scripts and create wiki pages for them in the near future.
Twiddler is currently working on creating some masternode setup guides (as requested by many of you). While doing this, he is also extending the wallet source code, adding some additional debugging output to make it easier to troubleshoot and set up new masternodes.
We currently only have 23 masternodes up and running, so running a masternode will be very lucrative at this stage. Masternodes will be receiving 40% of all newly generated currency (PoW and PoS blocks).
Yours, team swipp
Once we reached 140,000, all masternodes went offline. Started mine again, as have a few others, but it looks like masternodes aren't getting any rewards now. UPDATE: Maybe I spoke too soon; POS rewards look to be working. Watching. Weird though. Most of the recent POS masternode reward has been going to one address (SboeGLMo3mDvr8PHMnqSzQKbpyhqhJwQKF) |
|
|
|
Recently Znffal came up with an idea for us to lease out franctional sanctuaries to those who cant afford a full sanctuary.
I was thinking of potential ways to make this happen and here is what I have so far:
The pool could offer two new services: Sanctuary technology leasing, and Fractional Sanctuary leases with Dividends.
For STL, you spin up a node on a provider like vultr and set it up per the information given by the pool, the pool provides the data on the config page. Then you are paid weekly for the technology lease.
The second side of this, is the FSL. (This is for the average end user who wants the investment.. So we have a one-to-many relationship from FSL->STL. It might take 40 FSLs to fill up an STL). In this case you sign up for a certain quantity of 1000's that you can afford, (that is BBP * 1000),
and you become a leaseholder on record assigned to an STL ID, and you send this fractional escrow to the address the pool provides on the page, and at that point, you start receiving dividend payments based on your investment amount
automatically as long as the escrow remains in the investment.
The pool then combines all the BBP received for an STL into one transaction and creates an escrow vout for it and saves it (this is used to populate the page for the next STL).
So my first question is, what do you think is fair compensation for the STL? They would pay $5-$10 a month to lease the vultr node, and they only have to set it up once, but then they do have to reboot it every time they see new start required. So I was thinking maybe $30 for setup + $20 a month for the vultr lease renumeration + $10 a month for restarts = $60 a month. We could then convert that to a percentage, maybe that is 30% of the average deal. Once we know the percentage we could do something like this: 30/60/10: 30% to the STL, 60% to the FSL pool, and 10% to the pool....
Anyway, I think it would be a pretty cool hit-- also we could offer this as a way to "park" extra BBP for extra investments that happen to be laying around.
One thing I wanted to note: The STL would be the one to vote for the sanctuary, so that would be part of their responsibility.
Hi Rob, I like this idea a lot. I think that the effect of this would be to reduce the number of "stagnant" coins in wallets and on exchanges which is beneficial for the holders of BBP and for its price, which is good for the orphans, the project (i.e. IT budget), and the investors. It would also help more in the community to feel that they are getting some value from their coins and to feel more connected/involved. Regarding specifics of your idea/plan. I like the idea of having the STL and FSL. The voting rights was a potential issue that you have resolved by giving that to the STL. A few points/questions: 1. I assume that the STL would not start a masternode until all FSL spots are filled? i.e. the full 1,550,001 BBP has been raised. 2. What requirements would an STL need to have (aside from renting and running a server, voting)? I propose that they would need to contribute a % of the required BBP (required FSL) for their node. For example, maybe they need to put in 10% of the FSL (roughly 150k BBP coins) to run an STL. I can imagine a situation where it is more profitable to run an STL than it is to mine BBP which seems less than ideal. Having the STL contribute some eskrow also would reduce this issue. 3. The address that all members would send their portion of FSL to, would this be an address controlled by the pool? This seems better than an address controlled by the person running the STL. This mitigates the "trust" issue. 4. My opinion is that 30% for the STL is a little high, or at least, this should change to reflect the changing price of BBP. For example, if one day the 30% is roughly $60, and then we go x10, the STL is effectively being paid $600 a month. Maybe a one time set-up payment of $30 (perhaps taken from the first masternode payment), then $20 a month for the vultr lease renumeration + $10 a month for restarts = $30 a month or roughly 15%. I think the setup fee should just be for the first month... I am a bit torn on this point as they are providing a service that would otherwise not be available to the FSL contributors. Hmmm, tough one. 10% seems fair for the pool to host the service. EDIT( thought of a number 5.) 5. What happens if people want to withdraw their portion of the eskrow? Does the Masternode have to shut down until a replacement is found? Or do we implement a fixed term contract? i.e. a month long contract and you cannot withdraw your FSL contributions until the end of the month/contract? In principle I think it would make a lot of people happy that their coins are actually being put to use. The time-frame is pretty tight, when could such a service be implemented? Thanks! Have you come across MUE? It needs something like 500,000 coins for a masternode which is quite a lot of cash (was, at least, before the price dropped a lot) and their service, mymue.com, which fractional shares for 10,000 coins. |
|
|
|
NEW WALLET RELEASE 2.1.0 (Yggdrasil) Hello everybody!
As promised, here is the next wallet release with improved masternode payouts and many fixes and improvements to the code base. We have decided to put the block break at block 140 000. The changes will kick in at this block. As before - anybody that has not yet updated when we reach this block will no longer be accepted onto the network.
This should give everybody ample time to get a masternode up and running in preparation for the big show.See you on the other side! As previously discussed, the next update will now focus on adaptive masternodes and masternode rejection of PoS payouts. Again, we hope to get this released some time after Christmas.
Yours, team swippGreat stuff teamswipp |
|
|
|
Can somebody clarify what happens after the bolded virtualenv venv command. The venv \ Scripts \ pip install -r requirements.txt
returns the following error message:
'venv' is not recognized as an internal or external command,
operable program or batch file.
--- below is the full instruction from desper:
Install Virtualenv by running pip install virtualenv
Download the sent and unzip to the directory C: \ sentinel (you can specify another, but for example here it will be this one)
We execute in the directory C: \ sentinel
virtualenv venv
venv \ Scripts \ pip install -r requirements.txt <--- executing command this shows the result in the venv error message
Editing sentinel.conf by specifying the path to monacoCoin.conf in the monacoCoin_conf parameter.
Create a C: \ sentinel \ sentinel.bat file with the following content:
@echo off
set HOME =.
cd С: \ sentinel
C: \ sentinel \ venv \ Scripts \ python C: \ sentinel \ bin \ sentinel.py
Create a C: \ sentinel \ sentinel.vbs file with the following content:
Install WshShell = CreateObject ("WScript.Shell")
WshShell.Run chr (34) & "C: \ sentinel \ sentinel.bat" & Chr (34), 0
Install WshShell = Nothing
This intermediate vbs-script is needed in order to not open the console window when executing through the task scheduler.
We add the action C: \ sentinel \ sentinel.vbs to the task scheduler (Control Panel -> Administration -> Task Scheduler -> Create Task ...)
Trigger indicate "Daily", repeat the task 1 min.
Have you tried the official sentinel instructions at https://github.com/monacocoin-net/sentinel ? I ask as it has a simpler set of instructions to install sentinel and get it working. The “simpler” set instruction is for Linux. I am asking for Windows. Ah, sorry. |
|
|
|
Can somebody clarify what happens after the bolded virtualenv venv command. The venv \ Scripts \ pip install -r requirements.txt
returns the following error message:
'venv' is not recognized as an internal or external command,
operable program or batch file.
--- below is the full instruction from desper:
Install Virtualenv by running pip install virtualenv
Download the sent and unzip to the directory C: \ sentinel (you can specify another, but for example here it will be this one)
We execute in the directory C: \ sentinel
virtualenv venv
venv \ Scripts \ pip install -r requirements.txt <--- executing command this shows the result in the venv error message
Editing sentinel.conf by specifying the path to monacoCoin.conf in the monacoCoin_conf parameter.
Create a C: \ sentinel \ sentinel.bat file with the following content:
@echo off
set HOME =.
cd С: \ sentinel
C: \ sentinel \ venv \ Scripts \ python C: \ sentinel \ bin \ sentinel.py
Create a C: \ sentinel \ sentinel.vbs file with the following content:
Install WshShell = CreateObject ("WScript.Shell")
WshShell.Run chr (34) & "C: \ sentinel \ sentinel.bat" & Chr (34), 0
Install WshShell = Nothing
This intermediate vbs-script is needed in order to not open the console window when executing through the task scheduler.
We add the action C: \ sentinel \ sentinel.vbs to the task scheduler (Control Panel -> Administration -> Task Scheduler -> Create Task ...)
Trigger indicate "Daily", repeat the task 1 min.
Have you tried the official sentinel instructions at https://github.com/monacocoin-net/sentinel ? I ask as it has a simpler set of instructions to install sentinel and get it working. |
|
|
|
when will a new wallet released for each mn need different ip? if so, then do not hurry Hi! We have actually decided to allow masternodes on the same IP. However, the payouts received by these masternodes will be highly diminished. Read more about this feature here; http://www.swippcoin.com/specifications#adaptive-masternode-networkEssentially, it means that the more clumped together the masternodes are with other masternodes, the less payout they will receive. Masternodes that are very close to each other will more or less split the reward between each other. To our knowledge, Swipp will be the first cryptocurrency to feature something like this. Very exciting! The next release after this one will be a "masternode-maintenance" release - implemetning adaptive masternodes and optional PoS rewards (masternodes will be able to reject them). We plan to target this release some time after Christmas. Yours, team swipp Will there be a way to see where the existing masternodes are so that I can move mine to somewhere else if I'm currently somewhere crowded? |
|
|
|
no.
my sentinel was working fine earlier too.
and even now seems to be working.
check your sentinel conf. make sure its pointing to correct monocei conf
and make sure u have rpcuser and rpcpassword .
Btw way when u run sentinel, what do you get?
also, did you add cronjob to run it automatically?
Thanks for the help. I managed to solve the problem. I had an extra line in my sentinel.conf which was not a problem before the new wallet (or perhaps it was but I didn't know it). |
|
|
|
i was able to setup the MN using the monocei binaries.. also if done quickly, it is possible to make sure the status of the MN stays ENABLED. Windows ( local HOT wallet) 1) Download the windows wallet from https://github.com/monacocoin-net/monoeci-core/releases2) let it sync. 3) once sync is done, stop the old Monaco wallet and Monocei wallet on windows 4) copy paste wallet.dat and masternode.conf which comes from your MonacoCoin Core directory Copy and past monacoCoinCore.conf and rename to monoeciCore.conf 5) Start the Monocei wallet. Linux VPS 1) Download the linux binaries https://github.com/monacocoin-net/monoeci-core/releases. 2) Stop the linux daemon for monaco "./monacoCoin-cli -daemon" 3) start the monocei daemon "./monoecid -daemon" 4) let it sync for a while. 5) once sync is done, stop the monocie daemon 6) copy the monacoCoinCore.conf and rename to monoeciCore.conf 7) restart the linux daemon. PS: in case you have issues with running lnux daemon, please use the following files https://www.dropbox.com/s/rbtwujk0wma2i1s/monocei.tar.gz?dl=0these files are for ubuntu 16.04 setup sentinel as mentoined in dev guide. wait for some time and check you MN status. Just want to confirm that you renamed the old conf file to monoeciCore.conf as when I look in .monoeciCore the default file is just monoeci.conf updated , my file name is monoeci.conf. did a lot of copypaste Great. Did you have any problems with sentinel? I'm battling a WATCHDOG_EXPIRED problem which is stumping me. |
|
|
|
i was able to setup the MN using the monocei binaries.. also if done quickly, it is possible to make sure the status of the MN stays ENABLED. Windows ( local HOT wallet) 1) Download the windows wallet from https://github.com/monacocoin-net/monoeci-core/releases2) let it sync. 3) once sync is done, stop the old Monaco wallet and Monocei wallet on windows 4) copy paste wallet.dat and masternode.conf which comes from your MonacoCoin Core directory Copy and past monacoCoinCore.conf and rename to monoeciCore.conf 5) Start the Monocei wallet. Linux VPS 1) Download the linux binaries https://github.com/monacocoin-net/monoeci-core/releases. 2) Stop the linux daemon for monaco "./monacoCoin-cli -daemon" 3) start the monocei daemon "./monoecid -daemon" 4) let it sync for a while. 5) once sync is done, stop the monocie daemon 6) copy the monacoCoinCore.conf and rename to monoeciCore.conf 7) restart the linux daemon. PS: in case you have issues with running lnux daemon, please use the following files https://www.dropbox.com/s/rbtwujk0wma2i1s/monocei.tar.gz?dl=0these files are for ubuntu 16.04 setup sentinel as mentoined in dev guide. wait for some time and check you MN status. Just want to confirm that you renamed the old conf file to monoeciCore.conf as when I look in .monoeciCore the default file is just monoeci.conf |
|
|
|
/monoeci/sentinel# ./venv/bin/python bin/sentinel.py
-342: non-JSON HTTP response with '401 Unauthorized' from server
Cannot connect to monoecid. Please ensure monoecid is running and the JSONRPC port is open to Sentinel. sentinel.conf # specify path to monoeci.conf or leave blank
# default is the same as monoeciCore
monoeci_conf=/root/.monoeciCore/monoeci.conf
# valid options are mainnet, testnet (default=mainnet)
network=mainnet
#network=testnet
# database connection details
db_name=database/sentinel.db
db_driver=sqlite How to fix? All renamed, deleted, uploaded a new one. Same problem here. I don't know how to fix this. Hoping someone else has worked out how. |
|
|
|
Do we really need another masternode coin? How many do we already have?
No harm in focussing just on BTC and the major alts if that appeals to you more. |
|
|
|
|
Show Posts
