Papcio77
|
|
May 07, 2015, 03:31:07 PM |
|
SUMMER 2015 1CRAVE=1BTC !
|
|
|
|
borris123
|
|
May 07, 2015, 03:54:49 PM |
|
Ok so I got everything setup except the TOR part. I have the port forwarding ready I just don't know how to combine TOR into the mix. This http://www.cravecoin.info/master-node-guide/ doesn't really make it clear where or how to put that stuff into TOR. Can someone elaborate how to continue this setup please? Cheers! assuming you have installed tor browser bundle it will install it to the desktop. open the folder search for torrc and paste at the bottom HiddenServiceDir C:\Users\youruser\Desktop\Tor Browser\1 HiddenServicePort 9999 127.0.0.1:36896 HiddenServiceDir C:\Users\youruser\Desktop\Tor Browser\2 HiddenServicePort 9999 127.0.0.1:36897 the 36897 port can be changed to what port you want and forward these on the router. you can add as many as you want. restart tor once this is done and you will have created the hidden folders. search in these and for each one there will be host name. open it in notepad and this is what you use for ip along with the port. this should be your crave.conf with the minor changes. this is the adding some tor nodes rpcallowip=127.0.0.1 rpcuser=****** rpcpassword=********* maxconnections=25 rpcport=7500 server=1 listen=0 staking=0 port=36897 masternode=1 masternodeaddr=3rwjhfhas8fy3fdf.onion:36897 masternodeprivkey=jhafhsakjfhaljhflahfjklashkjfhsaf addnode=bmpgcs6rebbi4eae.onion addnode=d3uwttqdkzefzkgg.onion addnode=4ueei5enifrysvpz.onion addnode=z7cvdc6hh2opm47n.onion addnode=vfrunugv5nrpdxo3.onion addnode=4wdpnwwfdpwerjue.onion addnode=gpquwfjorzxrbt7o.onion addnode=rqpavbx3yy2jndzb.onion addnode=wnl7ezc55mp75spo.onion addnode=103.246.1.218 addnode=177.156.177.163 addnode=189.208.153.155 addnode=192.99.249.10 addnode=70.67.68.166 addnode=77.56.251.109 addnode=84.195.38.128 addnode=97.83.208.155 addnode=3coul74zxjuvbzec.onion addnode=pts3gm375hcmfphl.onion addnode=wxembbzxiti5unh6.onion addnode=lbbqcqmqjtg3ximh.onion addnode=4jzj5gxgilizlf6n.onion addnode=ssu6rizp6o5wgspj.onion addnode=d6sh33syl4kp6n5u.onion addnode=e5ant2t56yyu6iu5.onion addnode=7g2jsuslm7sffbtn.onion Well I did everything you said, got the hostnames and put em with the ports in the right places, but it doesn't work still says unable to connect to the new 38947139874.onion:forwardedport in the console I spent hours trying to get it to work also. The other day it messed up and i dunno why then suddenly started working again after changing ports oinion address. Are you connected to tor network? Make sure your firewall has enabled access. You have tor browser running (Basic things you probably done but worth a check) I don't think you will get anyone say what the problem is but that is how it is done. I asked loads of questions and people tried to help as I am but it made no difference. Start again. Make a new wallet follow the steps again. Use the adrenaline tab to create your node and conf. add the ports and onion address and give it another go. Took me days to get it work. Was working at one point then stopped a few times.
|
|
|
|
DiCE1904
Legendary
Offline
Activity: 1118
Merit: 1002
|
|
May 07, 2015, 04:15:25 PM |
|
Hmm didn't help, I keep getting stuck on 32713. Any suggestions?
|
|
|
|
Starin
|
|
May 07, 2015, 04:28:27 PM |
|
There is a dropbox upload that passed that block. You can find it in the topic. Download it.
|
|
|
|
CDarvin81
Member
Offline
Activity: 81
Merit: 10
|
|
May 07, 2015, 04:33:34 PM |
|
Hmm didn't help, I keep getting stuck on 32713. Any suggestions? just wait, i had the same problem after some hours the sync goes by...
|
|
|
|
EmilioMann
Legendary
Offline
Activity: 2184
Merit: 1028
#mitandopelomundo
|
|
May 07, 2015, 05:18:58 PM Last edit: May 07, 2015, 05:37:28 PM by EmilioMann |
|
Hmm didn't help, I keep getting stuck on 32713. Any suggestions? just wait, i had the same problem after some hours the sync goes by... this way is much more fast: EDIT: I'm updating the blockchain for today, will be ready in minutes EDIT2: Updated!
|
|
|
|
Mrpumperitis
Legendary
Offline
Activity: 2814
Merit: 1075
|
|
May 07, 2015, 05:53:11 PM |
|
blur period almost over...How do you use yours.... crave to nodes? crave for a market? burn for anon blur? pos on pc? android mob pos?
|
Bitcoin - Blockchain 1.0 (2009) Ethereum - Blockchain 2.0 (2015) Partisia - Blockchain 3.0 (2021)
|
|
|
trader19
Legendary
Offline
Activity: 1232
Merit: 1001
|
|
May 07, 2015, 07:00:42 PM |
|
blur period almost over...How do you use yours.... crave to nodes? crave for a market? burn for anon blur? pos on pc? android mob pos? i do.... crave to nodes? burn for anon blur? pos on pc?
|
|
|
|
|
DiCE1904
Legendary
Offline
Activity: 1118
Merit: 1002
|
|
May 07, 2015, 07:14:08 PM |
|
|
|
|
|
burner640k
Newbie
Offline
Activity: 12
Merit: 0
|
|
May 07, 2015, 07:31:58 PM |
|
OK, so I took a break from looking at it but now am back again trying to figure out why I was not credited Blur for the Crave I burned using darkpoold (block 52061, hash 1a278074b96bc61f913c0df3afca88c5fd0771757e2f02b171adf9bc6553001d, address CDssAhibe5m4hx3yMyi5TuxrqrSDuJRwqk).
I noticed that someone else may have run into the exact same problem as me, though I do not see them posting here. Whoever burned 13.99994986 Crave from address BvEeWXL6qz3YXRmBQbbh25ri4uQudpD67H at block 53204 you did not get any Blur.
In looking at that I noticed that both that person and I did the same thing, we burned all the Crave we had at our address, no change. Every other burn that I see has change. So maybe the bug with darkpoold is that if the burn does not have change it does not get recognized?
So after even further digging my prior thought above is incorrect, the problem of my missing Blur is not because I burned all the Crave at that address. However I think I am narrowing in on the problem that has plagued my burn. I am not a programmer but Python is easy enough to read through and follow to get an idea of what is going on. When darkpoold tries to match a vout to an input it grabs the transaction id of the input and then looks back at that previous transaction that happened in an earlier block. But when it goes to figure out what address in the prior block matches that output it uses the same function for getting the address as it does for the vout. This function requires asm to have 5 elements and if it does not it rejects it. In most cases this has been true so it processes fine. Unfortunately for my burn, block 52061, darkpoold looks at the first input and gets the transaction id for that, b03b0fe5b13cf3f506b52027876dbfde089a7a84e3cd49167ae5679df1f0bcf0. It then looks at that transaction which is for block 49674 and tries to match an output from that block to an input in the burn block, 52061. It finds the correct match, the 3rd vout in that transaction. After this it then tries to find what address that vout went to. However the get_address function calls the get_pubkeyhash that expects the asm to have 5 elements but my vout from that block, block 49674, only has 2 elements. So it rejects that and does not report my address so the burn fails. It looks like when getting addresses for the vin's in a burn block it should not have the same requirements as the vout for the burn block. darkpoold controls the vout format of the block but it does not control how all the transactions that came in are formatted. This has been quite a learning experience but I think I am getting close to why my 520 Crave burn was not recognized by the network. The good news is if I am correct if darkpoold gets patched then my Blur should show up if the database is rebuilt.
|
|
|
|
trader19
Legendary
Offline
Activity: 1232
Merit: 1001
|
|
May 07, 2015, 08:24:15 PM |
|
OK, so I took a break from looking at it but now am back again trying to figure out why I was not credited Blur for the Crave I burned using darkpoold (block 52061, hash 1a278074b96bc61f913c0df3afca88c5fd0771757e2f02b171adf9bc6553001d, address CDssAhibe5m4hx3yMyi5TuxrqrSDuJRwqk).
I noticed that someone else may have run into the exact same problem as me, though I do not see them posting here. Whoever burned 13.99994986 Crave from address BvEeWXL6qz3YXRmBQbbh25ri4uQudpD67H at block 53204 you did not get any Blur.
In looking at that I noticed that both that person and I did the same thing, we burned all the Crave we had at our address, no change. Every other burn that I see has change. So maybe the bug with darkpoold is that if the burn does not have change it does not get recognized?
So after even further digging my prior thought above is incorrect, the problem of my missing Blur is not because I burned all the Crave at that address. However I think I am narrowing in on the problem that has plagued my burn. I am not a programmer but Python is easy enough to read through and follow to get an idea of what is going on. When darkpoold tries to match a vout to an input it grabs the transaction id of the input and then looks back at that previous transaction that happened in an earlier block. But when it goes to figure out what address in the prior block matches that output it uses the same function for getting the address as it does for the vout. This function requires asm to have 5 elements and if it does not it rejects it. In most cases this has been true so it processes fine. Unfortunately for my burn, block 52061, darkpoold looks at the first input and gets the transaction id for that, b03b0fe5b13cf3f506b52027876dbfde089a7a84e3cd49167ae5679df1f0bcf0. It then looks at that transaction which is for block 49674 and tries to match an output from that block to an input in the burn block, 52061. It finds the correct match, the 3rd vout in that transaction. After this it then tries to find what address that vout went to. However the get_address function calls the get_pubkeyhash that expects the asm to have 5 elements but my vout from that block, block 49674, only has 2 elements. So it rejects that and does not report my address so the burn fails. It looks like when getting addresses for the vin's in a burn block it should not have the same requirements as the vout for the burn block. darkpoold controls the vout format of the block but it does not control how all the transactions that came in are formatted. This has been quite a learning experience but I think I am getting close to why my 520 Crave burn was not recognized by the network. The good news is if I am correct if darkpoold gets patched then my Blur should show up if the database is rebuilt. interesting information, thank you for sharing. hope u get your BLUR back. btw. around 400 Blocks until burn period finishes around 10hours to go...
|
|
|
|
crypto research
|
|
May 07, 2015, 08:26:16 PM |
|
This fud/troll stuff is nuts. Maybe we need to take a day to cool off Without you we would not get anywhere so take you some rest.
|
|
|
|
DiCE1904
Legendary
Offline
Activity: 1118
Merit: 1002
|
|
May 07, 2015, 09:15:06 PM |
|
Anyone else not getting any i2p-crave network connections?
|
|
|
|
rocoro
Legendary
Offline
Activity: 938
Merit: 1000
|
|
May 07, 2015, 09:23:06 PM |
|
Anyone else not getting any i2p-crave network connections?
Did you do this? Setting up your client to use I2P Your traffic will be open for anyone to inspect if you run the Crave client over clearnet. If you would like to hide the fact that you are using Crave, as well as the physical location from where your Crave traffic originates, you should set up your wallet to connect only to the I2P darknet. To do this, download and install the I2P router(see below). After starting the router, you will need to enable the SAM application bridge. In the I2P web interface ( http://127.0.0.1:7657/configclients), click on the box to automatically run the application bridge at startup, and then click on "start". By default, the SAM application bridge listens to 127.0.0.1 on port 7656. If you need to change this behavior, this can be done in one of three ways: - From the preferences menu in the Crave graphical interface, click on I2P, and then modify the IP number and port for the SAM application bridge. For the changes to take effect, restart the application.
- Edit the variable clientApp.1.args in the file clients.config that is located in your local I2P folder and then restart I2P.
- From the command line, start the Crave daemon (usually named craved) by specifying the following options: -samhost=<ip or host name> and -samport=<port>. For more options, use the command Craved --help.
Once this is done, start the Crave client, open the application preferences, click on the I2P menu, and then click on the button "use I2P only". Close the application and relaunch it. At this point, all your traffic will be encrypted and pass through the I2P network. Please note that it will take several minutes to make connections to the I2P network when starting I2P for the first time. Where to download I2P The official I2P release can be downloaded here: https://geti2p.net/en/download. The Abscond bundle is an easy to install software package with all you need to connect to I2P and let you use the most common features. It can be downloaded here: https://hideme.today/dev/.
|
|
|
|
DiCE1904
Legendary
Offline
Activity: 1118
Merit: 1002
|
|
May 07, 2015, 09:38:51 PM |
|
I did, i got Bitcoin-client showing under tunnels also. Just nothing on the actual crave client. hmm
|
|
|
|
|
|
jasemoney
Legendary
Offline
Activity: 1610
Merit: 1008
Forget-about-it
|
|
May 07, 2015, 11:14:23 PM |
|
come to slack https://cravecoin-slack.herokuapp.com/I will try and look into this with you my name there is thesherpa
|
$MAID & $BTC other than that some short hodls and some long held garbage.
|
|
|
NobodyYouKnow
|
|
May 07, 2015, 11:15:43 PM |
|
More like you're a useless prick. I'm a very busy man, I don't have time to waste on this shit, yet because I believe in the technology I figured I'd get involved and this is how you welcome me to your community after I've spent days trouble shooting this terribly constructed and horribly inconvenient system for setting up a masternode. Here you go Mr. Goofhead, enjoy the pic, it will suit your level of IQ better. Now MAYBE I can get some assistance here.. thanks.
|
|
|
|
|