I could use some help running a node...
I compiled bitmonerod and made a ~/.bitmonero folder (putting downloaded blockchain.bin and an old wallet.bin I have into it).
when I run a node I see this being repeated:
2015-May-16 08:05:21.827009 [P2P0]Failed to connect to any of seed peers, continuing without seeds
[/s] how to get seed node or peers?
Also the blockchain.bin obviously doesn't get used:
2015-May-16 08:05:20.435886 Blockchain initialized. last block: 0, d1046.h1.m5.s20 time ago, current difficulty: 1
Do I have to import blockchain.bin somehow?
EDIT: I got help on irc #monero, so this is solved. https://getmonero.org/getting-started/running doesn't help at all. It's extremely light on info and doesn't offer any information about configuration and/or troubleshooting. Frankly it's quite frustrating, I can't find any useful information on configuring / running a node. I would be grateful if someone could point me to some documentation. README.md doesn't give info beyond building, either. My wallet doesn't work either:
~/bitcoin/monero\> build/release/bin/simplewallet Creating the logger system bitmonero wallet v0.8.8.7-21a72bd Specify wallet file name (e.g., wallet.bin). If the wallet doesn't exist, it will be created. Wallet file name: /home/user/.bitmonero/wallet.bin Error: failed to open wallet "/home/user/.bitmonero/wallet.bin". Keys file wasn't found
am I missing another file to complete the wallet? Is it an old incompatible format?
Any help is appreciated.
EDIT was missing key file
|
|
|
At large solo miner with maybe 0.1% or 0.3% of the hash rate could start to inject very large 1GB blocks every 200 or 400 blocks or so, but in that case I could very easily see the rest of the pools agreeing to ignore those massive blocks. And even if they didn't coordinate to ignore them, the large blocks would propagate so slowly they might not be included anyway. (The attack requires transmitting a full block since Gavin's IBLT wouldn't help here).
ah, of course. IBLT doesn't help the rogue miner because his transactions haven't been broadcast. And he can't broadcast because then he risks losing the tx fees. I had overlooked that.
|
|
|
how about offering help instead of demanding and criticising?
|
|
|
http://www.fuw.ch/article/die-zweite-verheissung-von-bitcoin/Eine Blockchain ohne Coin macht ueberhaupt keinen Sinn. Wie soll denn eine Blockchain ohne Reward funktionieren? Irgendwie muss doch ein Anreiz gegeben werde. Minen dann Banken gegeneinander? Oder bin ich schon zu alt in dieser schnelllebigen Welt? Ich kapier es echt nicht! Bin gespannt auf die Loesung der Finanzhipster. Auf jeden Fall ist "Blockchain" gerade trendy. Der Begriff "blockchain" ist ein Trojanisches Pferd.
|
|
|
*rubs eyes* *looks price* *scratches head*
|
|
|
Error compiling Cython file: ------------------------------------------------------------ ... cdef extern from "stdlib.h": void free(void* ptr) void* malloc(size_t size)
cdef extern from *: object PyUnicode_FromWideChar(const wchar_t *w, Py_ssize_t size) ^ ------------------------------------------------------------
hid.pyx:14:46: Expected ')', found '*' [b]hid.c:1:2: error: #error Do not use this file, it is the result of a failed Cython compilation.[/b] error: Setup script exited with error: command 'gcc' failed with exit status 1 cypher@ubuntu:~/python-trezor$ sudo python cmdtr.py set_homescreen -f kocicka.png Traceback (most recent call last): File "cmdtr.py", line 8, in <module> from trezorlib.client import TrezorClient, TrezorClientDebug File "/home/cypher/python-trezor/trezorlib/client.py", line 7, in <module> import mapping File "/home/cypher/python-trezor/trezorlib/mapping.py", line 1, in <module> import messages_pb2 as proto File "/home/cypher/python-trezor/trezorlib/messages_pb2.py", line 4, in <module> from google.protobuf.internal import enum_type_wrapper ImportError: cannot import name enum_type_wrapper which leads to same error above. does it matter that i'm running 32 bit? this error sticks out: hid.c:1:2: error: #error Do not use this file, it is the result of a failed Cython compilation.
maybe try reinstalling cython? some people suggest downgrading to cython 20: https://github.com/kivy/buildozer/issues/150
|
|
|
sudo apt-get install libprotobuf-dev The full procedure: Using myTrezor.com - disable the pin first!
sudo apt-get install git python python-dev python-setuptools cython libusb.1.0-0-dev libudev-dev libprotobuf-dev git clone https://github.com/trezor/python-trezor.git cd python-trezor sudo python setup.py install sudo python cmdtr.py set_homescreen -f kocicka.png (or the name of your 128x64.png file)
Set your pin back.
To go back to the original screen:
sudo python cmdtr.py set_homescreen why disable the pin? cmdr.py prompts you for it. You just need to visualize a keypad:
|
|
|
Realize the above comment from me was provoked by some arsehole who was offended that I posted after I said I thought I could exit the thread. So it is not something I would have said to you if not for the general animosity towards me in the thread from numerous individuals. You and others disrespected me from the start.
It takes a little more than that to offend me. You're quite full of yourself, but that's ok. You're easily provoked, that's also ok. Calling me an 'arsehole'... I can overlook it. Your whole attitude of riding into this thread on your high horse and 'prodding' people who I have come to hugely respect is pushing it, though. You're being a know-it-all and smartass and you should be clever enough to predict the reaction and you should be emotionally prepared for it. It seems you aren't and frankly name-calling is something I hadn't expected from you. Kinda sad. If you interpret a little tease as disrespect then that's entirely on you. [/quote]
|
|
|
I'd need to know what kind of image file to provide (size, format,...)
Any image of size 128x64. Python Imaging Library will take care of conversion into black-white. wonderful, thanks! the flying spaghettig monster looks impressed EDIT: or maybe it's shocked to find itself inside a trezor device is it possible to do this with 12.04 Ubuntu? python-Trezor doesn't seem to work for me it should work. are you getting a specific error? edit: what I did: ~/bitcoin/python-trezor\> ./cmdtr.py set_homescreen -f fsm_128x64.png
you also need recent enough firmware on your trezor (not sure which version), otherwise trezor will complain
|
|
|
what happened to this? To everyone, I think I've written all I needed to write. Thanks for reading and apologies if haven't managed my couth optimally. Good luck to everyone and hope to see you all on the other side of this chasm.
|
|
|
It is important to buy in as soon as possible
So someone reading that in Nov '13 (when you made the post) would've bought in right away and be 80% in the red now, still waiting for $2000. Yeah, you can always cherrypick. If you take the whole price history, and compare buying in immediately to any other buyin strategy, it's hard to find one that yields a better result, even if we didn't take the resources spent in forming and executing the strategy into account. SSS is a simple, passive strategy, suitable for long-term high variance +EV investments, done with small-to-moderate % of your portfolio. It's not intended for dealers, traders, gamblers or the like. Yes, I agree. I was cherry-picking, of course. Considering to look for a better buy-in strategy. Seems to me some sort of averaging strategy could beat all-in. I know this has been discussed before and it's a moot point until checked against the data, of course. btw: I found myself unable to hold back on buying during almost all of this bear episode of bitcoin. I'm basically dollar-cost-average buying all the time, maybe even increasing fiat-value of the buys as we go lower. The thoughts behind your savings plan have helped me on another front, though: I had been accumulating some Auroracoin over the last year of so (I still love that experiment and I'm really happy it looks like it's going to continue) and during the recent hype and price-hike in AUR_BTC (The last airdrop had ended and Baldur Odinson had burned the premine left over from the airdrops) I managed to get myself to ignore the greed and sell into the strength (first regretting it of course, but now - as we experience a slump - being quite content because I also sold the top and I was always "safe" against the hype ending). So: thanks for the simple savings plan, it's been good for me
|
|
|
What kind of money makes you a whale?
Bitcoin
|
|
|
If I had literally followed my plan, instead of buying back at a nice discount a year ago, the situation would be even better. So folks, do what I say, not what I do Load up on bitcoins (and monero) now as the scenario universe is heavily tilted on your favor, and be strict in selling on strength when it comes, and don't buy back in the subsequent slump (and of course, never ever sell on a loss). This only makes sense if the bottom is in. Otherwise it's a contradiction, no? Maybe like a year ago, we think it's a nice discount now, but it really isn't? EDIT: this is what your SSS post says about buying: It is important to buy in as soon as possible
So someone reading that in Nov '13 (when you made the post) would've bought in right away and be 80% in the red now, still waiting for $2000. I am involved in a new website that will distill my writings here to coherent articles. Launch is expected next month.
I applaud and look forward.
|
|
|
Some future day when the subsidy is near zero miners will refuse to mine a block unless it at pays for itself.
Interesting observation, never thought about it. Only if there's enough transaction fees to be had from the mem-pool would miners power up. In fact they might even mine a different sha-coin that offers some fees in the meantime. But disregarding that for a moment, what would the effect be? Since the overall effective hashrate is lower, difficulty would drop at some point and then the network would find blocks faster when tx load is high, slower when it's low. Would security suffer? My first thought was: yes, but then again you have the option to fend off an attack by making some high-fee transactions and thereby releasing more hashpower.
|
|
|
Everyone thinks you get more money selling slowly into the bids. Guess what? There aren't enough of them to sell thousands of coins. You'll slip as you chase them down. Best to bite all the bids that are there. Bulls do the same thing on the upside as I'm sure you've seen.
Also bids get pulled once you start eating and price starts to drop. Best take a sizable bite in one go.
|
|
|
I agree this has potential. It'd be a clean, permanent solution with nothing arbitrary about it. Sometimes we just don't see the simple things? Too-large-blocks are already disincentivized by their slow propagation and resulting higher orphan risk. I read that many pools already use a "soft limit" well below 1 MB because of this. It would probably make most sense for a miner to calculate the cost of the orphan risk (needs some assumptions, I guess) and contrast that with the potential additional tx fees being earned and make tx inclusion decisions based on that calculation. what will happen when block propagation will be O(1)? (see: https://gist.github.com/gavinandresen/e20c3b5a1d4b97f79ac2) Yes, I know. Also consider: the "IBLT block transfer mode" can already be done among miners/pools without us even knowing. So maybe the disincentive of large blocks doesn't even exist.
|
|
|
I agree this has potential. It'd be a clean, permanent solution with nothing arbitrary about it. Sometimes we just don't see the simple things? Too-large-blocks are already disincentivized by their slow propagation and resulting higher orphan risk. I read that many pools already use a "soft limit" well below 1 MB because of this. It would probably make most sense for a miner to calculate the cost of the orphan risk (needs some assumptions, I guess) and contrast that with the potential additional tx fees being earned and make tx inclusion decisions based on that calculation.
|
|
|
lol, couple pages back (5 or 6, after the drop), some noob accounts came in here yelling "ponzi". wtf is this? 2011?
|
|
|
Still bored errybody? I was asleep at the time ;-|. Now what? Boring again?
|
|
|
|