Search content
Sort by
Showing 20 of 194 results by roundrobin
Re: [ANNOUNCE] Abe 0.7: Open Source Block Explorer Knockoff
Ufff, people still fight with getting old Abe to work?
Why not use something simple to install like Insight or RPC Ace?
Why not use something simple to install like Insight or RPC Ace?
Insight is quite a challenging or rather problematic block explorer to set up.
In the the newer versions of bitcore it's even more unclear where to go to re-configure it to match your coin's properties if you already managed to change it from SHA to whatever algo your coin uses.
Those using older insight/insight-api/bitcore versions which were easier to configure, will notice that Insight runs no longer than 15 minutes before losing its connections to the insight api/bitcore due to a memory leak, stalling the Node process and ultimately clogging up the whole server if not restarted right after the 'crash'. I guess it's doable with enough resources, time and effort. The Reddcoin and Startcoin team managed to get it done. Startcoin crowdfunded the conversion to X11 POW for START on Startjoin to get a pro do it for them. I don't know about Reddcoin's team though.
Furthermore, Bitpay ignores every single "issue" on Github or question asked on their Labs forum if you even dare to include the word altcoin or a subject that is something else than Bitcoin concerning their products. I'm waiting for over a month now concerning this memory leak. They don't even take 5 seconds to tell you to fuck off with your altcoin. Nothing. I find this quite disrespectful. You are free to choose not to support users who use your product in a different way than intended, but at least have the decency to write a statement about it and put it on the website or the fine print at the bottom: "We do not support altcoins". Is that too difficult?
Until they embrace altcoins or that a skilled developer decides to build a universal block explorer, Abe is basically the only accessible block explorer we have.
RPC Ace is universal and doesnt care for coin algorithm. Takes 1 minute to setup. But yeah it's not "advanced" explorer in the way Abe is.
Re: [ANNOUNCE] Abe 0.7: Open Source Block Explorer Knockoff
hi,
can anyone post a download link for abe.sqlite bitcoin (or a trick to make it faster), this shit takes forever to finish. im still on block_tx 182130 3564583 since 7 days
just dont use sqlite, its not meant for a serious DB, just for something small to play around/beginners. bitcoin is huge and dosnt fit this space.can anyone post a download link for abe.sqlite bitcoin (or a trick to make it faster), this shit takes forever to finish. im still on block_tx 182130 3564583 since 7 days
You are blatantly wrong and misinformed. You should not make comments like those because people who (just like you) don't know better will take it for truth.
Sqlite does not offer a queing gateway for queries like postgresql or mysql does, but in terms of inherent concurrency it is in fact much more capable than both postgres and mysql is, and with notably higher performance while still consuming less memory. For sheer size of databases, it is faster and more efficient, but only for intra-process concurrency. Contrary to common believe, sqlite does have a transaction log, and it is suitable for multi-process concurrency just not on the same scale as a dbms with a queing gateway.
Re: [ANNOUNCE] Abe 0.7: Open Source Block Explorer Knockoff
hi,
can anyone post a download link for abe.sqlite bitcoin (or a trick to make it faster), this shit takes forever to finish. im still on block_tx 182130 3564583 since 7 days
can anyone post a download link for abe.sqlite bitcoin (or a trick to make it faster), this shit takes forever to finish. im still on block_tx 182130 3564583 since 7 days
Yeah i feel your pain, I've been there :PP If you are not looking in-depth details of inputs or tracking addresses and already have the blockchain, check out RPC Ace explorer as it doesn't need installation no database etc.
Re: [ANNOUNCE] Abe 0.7: Open Source Block Explorer Knockoff
can Abe work with fresh algorithm? which policy can I use for fresh algorithm.
Hi, WildWestCoin needs in the new Block Explorer, who can help?
Write in WEST topic, please:
https://bitcointalk.org/index.php?topic=607493.0
Write in WEST topic, please:
https://bitcointalk.org/index.php?topic=607493.0
Does anyone know the parameters needed for Guldencoin(NLG) - https://bitcointalk.org/index.php?topic=554412.0
I want to run ABE for NLG. Thanks!
I want to run ABE for NLG. Thanks!
Abe docs (and example confs) explain how to adapt for a new chain, there are some old unfixed problems though and you may need to edit the internal datastore.py to make it work. Another solution is to use an explorer which does not care for algorithm and work with all blockchain, like RPC Ace: https://bitcointalk.org/index.php?topic=686177.0
We are almost there
Yep first halving tomorrow evening.
New High performance SOLCOIN Mining pool. http://hashgoal.com/pool/SOL/
Hey, It response no Solcoin pool.
What happen to ur pool ?
Looking at his main page alot of pools still there but he removed SOL pool, maybe because people don't want to move away from omargpools and so.
New High performance SOLCOIN Mining pool. http://hashgoal.com/pool/SOL/
Very slick p2pool frontend, what is the name of it? Also I saw your pool using 0.8.6.1 which is pretty old. Maybe you want to run a new version of Solcoin since much changed and got fixed. 0.8.7.4 is the current version.
Re: [ANN] FedoraCoin (TiPS); New style, new services, same unique features
Not the rpc-ace type, it's a really light explorer and I only set it up to work as a backup. I'll get to work on an Insight type block explorer soon.
Actually you can enter both hash or block number in the URL of RPC Ace explorer and it take you right to the block.Yeah it does not keep a database so not possible to backtrack an address but the author has said he has a database version he maybe releases soon. It would probably have ability to check an address's history.
Re: [ANN] FedoraCoin (TiPS); New style, new services, same unique features
Will it be possible to enter address or hash on block explorer?
Not the rpc-ace type, it's a really light explorer and I only set it up to work as a backup. I'll get to work on an Insight type block explorer soon.Actually you can enter both hash or block number in the URL of RPC Ace explorer and it take you right to the block.
Re: [ANNOUNCE] Abe 0.7: Open Source Block Explorer Knockoff
Good evening
I've prepared a VM with Ubuntu Server 14.04/1GB RAM/8GB VDI and had some fun setting it up to host ABE. It's very slow, but I that's due to the hardware it runs on (old 6 year old laptop with a 1.6ghz athlon neox2 and 4GB ram. Anyway, since my tests are successful, I was thinking to host it somewhere, but I have no clue about the hardware requirements needed. When I look at VPS solutions like Digital Ocean's 5$ and 10$ packages, they look similar to my VM, memory-wise, but I don't know about the other virtualized hardware.
I'd like to avoid getting Error 500's or time-outs as the daemon will be running in the background to keep it updating at any time.
On my VM, the wallet daemon takes up to 15% of the cpu load, python around 35% and postgresql is sometime at 80% while loading blocks in the database (in huge chunks) during the initial loading.
When no blocks are added as the come, it's around 10% for postgresql and python, daemon runs at <2% load.
If I query the block explorer for an address, it pyhon gets spikes as high as 45%, postgresql 50% and apache2 45%...
So, I'm wondering what the minimum hardware requirements (or VPS equivalent) are to host this kind of service.
Also, is there a way to filter out the staking transactions?
I also think there's a problem. When looking at transaction details, it show always the same kind of addresses for any sender and receiver, for any transaction... for the first one to the last one in the whole blockchain. But I can query a specific transaction and it shows all the transactions that I see in my wallet as well. Did I miss something during the setup. Is there an (d)e(n)coding error? The address receiving those 5000 coins should be the one in my sig. M.....eXe iso 6KZ...PW9
Thanks for insights
I've prepared a VM with Ubuntu Server 14.04/1GB RAM/8GB VDI and had some fun setting it up to host ABE. It's very slow, but I that's due to the hardware it runs on (old 6 year old laptop with a 1.6ghz athlon neox2 and 4GB ram. Anyway, since my tests are successful, I was thinking to host it somewhere, but I have no clue about the hardware requirements needed. When I look at VPS solutions like Digital Ocean's 5$ and 10$ packages, they look similar to my VM, memory-wise, but I don't know about the other virtualized hardware.
I'd like to avoid getting Error 500's or time-outs as the daemon will be running in the background to keep it updating at any time.
On my VM, the wallet daemon takes up to 15% of the cpu load, python around 35% and postgresql is sometime at 80% while loading blocks in the database (in huge chunks) during the initial loading.
When no blocks are added as the come, it's around 10% for postgresql and python, daemon runs at <2% load.
If I query the block explorer for an address, it pyhon gets spikes as high as 45%, postgresql 50% and apache2 45%...
So, I'm wondering what the minimum hardware requirements (or VPS equivalent) are to host this kind of service.
Also, is there a way to filter out the staking transactions?
I also think there's a problem. When looking at transaction details, it show always the same kind of addresses for any sender and receiver, for any transaction... for the first one to the last one in the whole blockchain. But I can query a specific transaction and it shows all the transactions that I see in my wallet as well. Did I miss something during the setup. Is there an (d)e(n)coding error? The address receiving those 5000 coins should be the one in my sig. M.....eXe iso 6KZ...PW9
Thanks for insights
Abe will run ok on Digital Ocean's 1GB RAM VPS ($10/month). It is possible to get it to work ok also on 512MB RAM if you set up swap memory, pick the right distro and disable some unnecessary things to conserve memory use. Don't worry about CPU usage because even if Abe is written in Python which is a shit slow performing language that is not where problem or bottleneck with Abe is, it will run good on some old Pentium 3
If you want smaller footprint blockexplorer (but with some limited feature) check out RPC Ace https://bitcointalk.org/index.php?topic=686177.0Your pool seems faliure, plaese check it!
Looks like working now, they have 1.6 gh/s and putting Solcoin over 2 gh/s for the first time. Difficulty over 90!
Big number of dead shares on the p2pool, I think miners are not setting their difficulty correct. For anyone using the p2pool, you should set preferred difficulty for your miner by putting +DIFFICULTYNUMBER after your payment address, and you can calculate best difficulty for your hashrate like this:
Multiply your worker's MH/s with 0.001164 to get the difficulty number
Example:
With a 1.5 MH/s miner, best difficulty will be 1.5 * 0.001164 = 0.001746, so I configure my miner with username SOLCOIN_ADDRESS+0.001746
If I have a 30 MH/s miner...... 30 * 0.001164 = 0.03492 .... my p2pool username should be: SOLCOIN_ADDRESS+0.03492
It's important you set this correct when mining on any p2pool, because it can mean a difference of up to 15-20% efficiency. Also remember to set number of queued shares to 0, low scan time and low expiry. These options have different names depending on what miner software, and some miners don't support all of them. Typical cgminer options for p2pool is "--expiry 2 --scan-time 2 --queue 0".
Multiply your worker's MH/s with 0.001164 to get the difficulty number
Example:
With a 1.5 MH/s miner, best difficulty will be 1.5 * 0.001164 = 0.001746, so I configure my miner with username SOLCOIN_ADDRESS+0.001746
If I have a 30 MH/s miner...... 30 * 0.001164 = 0.03492 .... my p2pool username should be: SOLCOIN_ADDRESS+0.03492
It's important you set this correct when mining on any p2pool, because it can mean a difference of up to 15-20% efficiency. Also remember to set number of queued shares to 0, low scan time and low expiry. These options have different names depending on what miner software, and some miners don't support all of them. Typical cgminer options for p2pool is "--expiry 2 --scan-time 2 --queue 0".
Here is the omargpool failure: http://rpcace.solcoin.net/?108219
Check block 108213 in the middle with 640(!) transactions that piled up and next block after that took 3(!) hours when almost 80% of network hashrate went offline and the nice difficulty drop after that. Seriously miners you should spread out on the pools and configure failover, make use of the new Poolfinity pool and Solcoin team's own p2pool.
Check block 108213 in the middle with 640(!) transactions that piled up and next block after that took 3(!) hours when almost 80% of network hashrate went offline and the nice difficulty drop after that. Seriously miners you should spread out on the pools and configure failover, make use of the new Poolfinity pool and Solcoin team's own p2pool.
As more than half of the network hashrate is on OmarGPools we would like to remind miners that there is an official Solcoin P2Pool maintained by the Solcoin team
Ideal would be if miners spread hashrate out on the pools now with three pools available. Miners always fear low returns from long time between blocks so they mine on the biggest pool thinking it pays better but it's a false fear, even if only 3-4% of global hashrate is on one pool it usually yields 95-100% efficiency. Some of the "big fish" on omargpools should consider moving to the official p2pool or the new Poolfinity. This weekend showed the negative result of everyone mining in one pool when omargpool was dead for 24 hours or so, Solcoin dropped to 20% of its normal hashrate. Most miners didn't even have failover configured.
People following Solcoin should be interested to vote here to get Solcoin on coinwarz.com list: http://www.coinwarz.com/voting
Remember you can vote every hour, not just one time.
Remember you can vote every hour, not just one time.