 Show Posts
|
|
Pages: [1] 2 »
|
Open Source CCE 4.0: https://github.com/cryptocoinexplorer/Open-Source-CCE-4.0CryptoCoin explorer was started in late 2012 as a PPC explorer shortly after the PPC block chain went live. The PPC explorer was based on ABE with some modifications to allow ABE to work with the then new POS block chain. Eventually more explorers were added and the site became www.cryptocoinexplorer.com
After the first year a few things became apparent. ABE (Created by John Tobey - https://github.com/bitcoin-abe/bitcoin-abe): Before I go further, I want to give a big credit to John Tobey. At the time ABE was written, coin daemon RPC commands were not as advanced as they are today. ABE was a brilliant piece of software and is still largely used as a base for explorers to this day. In no way do I want to imply otherwise. John Tobey and his team have contributed greatly to the Cryptocoin community. ABE quite often would need to have its code modified to work with new emerging block chains. At the time, ABE would get its information by directly reading the blk database files. As new block chain technologies came out and fields were added or modified, ABE would be unable correctly read the files as it expected fields to be in certain byte positions from certain markers. If the database structure was not Bitcoin or Litecoin, it would have a difficult time parsing the block chain. ABE also needed to be able to natively hash. At the time it could hash SHA-256 and Scrypt. CCE (CryptoCoin Explorer): With CCE expanding, it was becoming increasing difficult to keep altering the code to work with more and more block chains. RPC commands were becoming more advanced and reached a point where all the information needed for an explorer could be retrieved from the coin daemon RPC. I decided to write a new explorer from the ground up that would get all the information from the daemon RPC thereby negating the need to have the explorer understand the block structure or hash algorithm. Using just configuration options, CCE can be made to work with almost all coins without the need to patch code. CCE was always a full block chain explorer, storing data in a mysql database as new blocks were accepted into the block chain. The database loader is triggered by the block notify daemon function and populates the database. The web server works with the database exclusively and does not communicate with the coin daemon. NOTE: Later versions added a couple of functions where the web server does communicate with the daemon, but those functions are not in the open source version. The first release of the new CCE was named CCE 3.0 and released on CCE in 2013. Later CCE 3.5 and eventually CCE 3.99 (A final patch version adding some of the core CCE 4.0 improvements) were released on CCE. These were all closed source. At the beginning of this year, I started working on CCE 4. This was to be a basic rewrite of CCE 3.5 with many features added and core code improvements. I also decided to release an open source version of CCE 4. This is a VERY BASIC version of CCE 4 and meant to act as a foundation for building an explorer, though it can be used as is. The closed source version being developed for CCE is based on the open source version, but is more robust and feature rich. Open Source CCE 4.0: https://github.com/cryptocoinexplorer/Open-Source-CCE-4.0 |
|
|
|
www.cryptocoinexplorer.comThis month starts the development stage of CCE 4.0. CCE 4.0 will be a major rewrite of large portions of CCE 3.5. Internal Goals:Improve efficiency of database loading and sorting Increase speed of the web server module. Decrease size and improve database structure and indexes.
Tentative New/Modified Features: Sponsor/Developer explorer customization. Sponsor/Developers will be able to change the look and feel of the explorer whenever they wish. Attributes like background image, coin image, table elements (border,backgrounds and text), and button/hyper-link settings. Each page and table will be independently set. The developer message box will be replaced with a whole developer/sponsor set page and explorer home page headline. Ability to parse and display TX messages in chains that support it. Add country of IP address in the coin daemon peers page. Removal of port display after IP address as it is not useful information. Plain text list of IP addresses for easy cut/paste into configuration files. Plain text display option for block,transaction, rich list, and ledger pages. Table sorting options. Add ABE compatible API alongside the current CCE API. Improve the output of some of the more complex data returns from the CCE API. Graphing of certain statistics. More features are being considered. If anybody has any requests for other features, please post here!A new official forum topic for general discussion of CCE has been made: https://bitcointalk.org/index.php?topic=922515.0
|
|
|
|
Cryptocoin Explorer is one of the oldest alt-coin explorers still in operation. When started almost three years ago , it was based on ABE. Since the middle of last year, it is now run on the CCE explorer software platform that I wrote. CCE is now at version 3.99 and development of version 4.0 has recently been announced. https://bitcointalk.org/index.php?topic=922521.0Coin developers and communities can sponsor their coins to have an explorer on CryptoCoinExplorer.com
Sponsorship includes the following: Setup of a CCE3 explorer for the sponsored coin. Hosting and maintenance of the explorer Developers Box access key. Access regulated by some basic rules of conduct. Use of the explorers coin daemon to use as a seed node through a custom altcointech.net address. This extra address allows the use of the daemon as a seed node if the explorer gets moved to a new server, or at a future date the need to separate the services arises. Please see the API page for a description of the API access that CCE3 provides. API InstructionsPlease see the sponsorship page for more information: SponsorshipCurrent coins on CCE: Bitbar Kilocoin Blakecoin Photon HoboNickels Bottlecaps Goldcoin Hyperstake Hempcoin Electron *Note: I have switched to a self moderated thread to keep the thread clean and relevant. For example, having old posts about bug reports that have been fixed clutter the thread. I have no desire to censor anything and appreciate all the feedback given. However, given the radical change in the environment of this forum over the last year, I will remove disruptive posts. This does not mean negative posts, but posts that are trollish and serve no real purpose or criticism. |
|
|
|
WWW.CRYPTOCOINEXPLORER.COMI am now locking this thread and the old CCE thread and starting a new main Cryptocoinexplorer thread. I am ready to release a patch that improves & adds features to the CCE3 API. Details to follow in the new thread. https://bitcointalk.org/index.php?topic=584847.0CCE will be converting over to CCE3 over the weekend- Explorers will be up and down over the weekend
- A few of the explorer conversions will present some difficulty due to missing or non-confirming RPC commands. These may or may not make the conversion
- Site owners need to be aware that the API is different in CCE3. I will explain the API in the next post.
- The API will be expanded over the next couple of weeks including activation of the developers message box as developers contact me and receive their API key.
- The business model has not been completely decided in relation to adding new coins. This will be decided after conversion and I get a feel about the reaction
Coins that will be a bit problematic: (If needed, this list will be updated as I convert the site) PPC - Though recently updated with a newer BTC base, the 'getrawtransaction' command still does not allow for non-wallet transactions. I have mentioned this a few times both publicly and privately before the new version came out. PPC is completely dead in the water as far as CCE3 is concerned until rectified. PPC will remain on CCE (It was the coin that started it all for CCE) though it may be delayed if I have to patch the coin daemon myself. BBQ - Does not have 'getrawtransaction' but does have 'gettransaction' and allows for non-wallet transactions. However, the 'gettransaction' output is non-standard and missing some key information. I cannot revert back to an ABE based explorer for this coin as ABE now has the habit of crashing quite often with this coin. I do not know if this coin has an active developer, but the daemon will need to be updated in order to remain on CCE. If I have to update the daemon myself, it could be some time before the coin appears back on CCE. Afternote: I will attempt to keep an ABE based explorer up for BBQ, but if it becomes too troublesome, I may have to pull it until a patch is released. FRC - No 'moneysupply' field with a variable block reward. This issue has been solved, though I do need a special version of the dbloader due to the way it reports coin values. The 'moneysupply' issues have been solved for all coins. I will be creating a new thread for CCE, but for now the old thread is located at: https://bitcointalk.org/index.php?topic=124303.0The CCE3 development thread:
https://bitcointalk.org/index.php?topic=262539.msg2804427
|
|
|
|
I have been noticing a trend of really bad configuration file examples lately. While most are harmless, one parameter poses a large security risk to the user. rpcallowip=* 1. rpcallowip is only needed in special situations where one wants to allow the client/daemon to accept RPC connections outside the localhost. Generally solo miners who want to point their rigs to a single daemon on the network. 2. rpcallowip=* tells the client/daemon to accept RPC connections from anybody-anywhere. If the rpcallowip setting is needed, restrict it to a certain IP address or network. For example: rpcallowip=192.168.1.* This will restrict connections to hosts 192.168.1.0 - 192.168.1.255(The typical private subnet used on home networks) Other oddballs: rpcport=<port> or port=<port> Unless you need to change the RPC or P2P port from the default in the client/daemon, there is no need for this. daemon=1 or listen=1 Any of these extra settings are not needed and they are on by default or in the case of daemon=1 normally passed as a command line option as it only effects the non gui command line daemon. A typical user configuration file only needs: server=1 This is even optional as it sets the QT client to accept RPC commands, but harmless if set and not used. Some QT clients need this to use the RPC console in the debug menu. rpcuser=<username> Required for the most part rpcpassword=<password> Required for the most part. Other useful parameters: addnode=<IP> This gives the client/daemon a node to try every time it starts. Useful for new coins with no seed nodes hard coded in the source, or new coins with few nodes. txindex=1 This tells the client/daemon to build a full transaction index and allow one to retrieve non-wallet transactions typically through the "getrawtransaction <txid> 1" command. If added after the client has already started building or has built the block chain database, the switch "-reindex" will need to be used one time after the parameter has been added. |
|
|
|
Some very large changes are coming to the Scifi Coin community.The next couple of weeks are going to be filled with new opportunity's and FUN!!
Why not take some time out of the rat race of this sub forum and take a lighter heart approach to crypto currencies, maybe even partake in a Scifi fantasy or two. 
We want to welcome everybody to the Scifi coin community, and see a more relaxed side to the crypto world. 
Please read about the changes coming at the Official Scifi Cryptocoin forum:http://scificointalk.com/index.php/topic,492.0.html This Thread is to keep everybody updated about the Star Trek inspired crypto coins and Scifi inspired coins in general. Please visit our official website and forum: http://www.scificryptocoin.org/http://scificointalk.com/index.phpKLINGON EMPIRE DARSEK The client has been rebuilt on a fresh Novacoin base with a couple of tweaks. TECHNICAL SPECIFICATIONS: Chain Type: Scrypt/POS Block Target Time: 1 Minute POW Block Reward: 3.5 PPC type re-targeting Trade confirm: 6 Blocks Coin maturity: 120 Blocks RPC Port: 8444 P2P Port:8443 Block one will be a super block of 285K coins. This is to replace the coins in the original chain through the KED REDEMPTION PROGRAM.At the time of block cut-off, approximately 285,000 Darsek had been mined. Windows QT: https://drive.google.com/folderview?id=0B0wumNRRq9LNVndqa05SYXNxOHc&usp=sharingGithub source: https://github.com/scificryptocoin/DarsekPools: www.kedcoin.comked.livechains.netExplorer: ked.cryptocoinexplorer.com
|
|
|
|
Darsek & Federation Credit CryptoCoin Mines Darsek Pool: http://kedcoin.comor http://www.kedcoin.comMining ports: LP - 3333 http://kedcoin.com:3333The Federation Credit pool: http://ufccoin.comor http://www.ufccoin.comLP Port: 4444 http://ufccoin.com:4444I am having a bit of a strange issue with the stratum port I use. For some reason it will detect candidate block submissions, record in the log , but never submit them to the daemon according to the daemons debug log. I have never seen an issue like this. So...This means that the pools will be LP for now until I can solve the stratum issue. I spent a large chunk of time fiddling with the stratum server , a few of the extra features still need to be worked on. For both pools-To do list: -Stratum support -Network hash rate display (The two daemons do not have a direct command for this, instead I have to write a bit of code to get it from mining info) -E-mail support (Mostly for confirmation-possible Notification feature in the future) -Star Trek theme customizations -Fix block explorer linking |
|
|
|
CryptoCoinExplorerThe CCE3 test has moved to test version 3.98!!https://bitcointalk.org/index.php?topic=262539.msg3177164#msg3177164All test explorers are now running test version 3.98 New in this version: Complete database integrity and automated recovery system Complete removal of all per coin custom coding in the modules. General clean-up and tighter code. Started basic code comment documentation. Primecoin http://xpm.cryptocoinexplorer.comGoldcoin http://gold.cryptocoinexplorer.comFederation Credits http://ufc.cryptocoinexplorer.comKlingon Darsek
http://ked.cryptocoinexplorer.com - Temporary Down until KED relauch Gold Pressed latinum http://gpl.cryptocoinexplorer.comCthulhu Offering http://off.cryptocoinexplorer.comBottleCaps http://cap.cryptocoinexplorer.comCubits http://qbt.cryptocoinexplorer.comI believe a separate thread is needed for the development of CCE III, as it is a large project not only in the sense of CCE, but as a new development tool for other developers. CryptoCoin Explorer III Update:
History:CCE started as the PPC explorer when PPC was released in August 2012. Note: About three weeks until the PPC one year anniversary August 16! Terracoin and Freicoin followed as they were released. The CryptoCoin Explorer site came online November 14, 2012 Novacoin, BBQ, Feathercoin and Bytecoin became part of CCE. Since this April: Bitbar, Digitalcoin, CHNCoin, JKC, Franko, Goldcoin, Worldcoin and Craftcoin have been added. CCE is now spread across two decent sized VPS. CCE has a Alexa global rank of 280,031. Although I do not have any detailed metrics installed on the site, I have seen estimates of 5000 – 10000 hits a day. The site sends out about 10GB of data a day over both servers. A couple of months ago I updated the look and feel of CCE which I called CCE 2. About a month ago I decided to write completely new explorer software from scratch. There were a few additions to the API being worked on and the bigger issue of resources versus the number of coins coming on the market. I also wanted to provide a one stop site for coin information as it became harder to search and find information for all the new coins. It became clear shortly after I put the first few explorers online, CCE became a trusted source for block chain information. I take that responsibility seriously, and part of the reasons for the rewrite is to give the community an even larger source of information in both number of coins and quantity of information. I also want both new and experienced alt-coin users to have a place to go and get links to official sources of information.
|
|
|
|
JKC - The Scrypt Coin with Super BlocksGithub: https://github.com/Hartland/JKC (Full fix for "warning" 12.20.2013) Windows Download: (UPDATED 12.29.2013)
https://drive.google.com/folderview?id=0B0wumNRRq9LNa2VOdDF2amtsa0E&usp=sharingThe new feature of this coin is that it added random coin size per block (see below), so even late in the game, you may still hit a block of 1000 coins! Like real gold mining, you may hit different block grade:-) Features: - Total coins will be around 107 millions - 1 minutes block target - Difficulty re-targets once per day - Coinbase: 50 coins per block. It will also be halved about every two years (every 1036800 blocks). - Mining will be shut down after 12 years. - In regular mining (after first 4 bonus days), there will be 1% chance a block will yield triple of the normal coins (e.g. in the first 2 years there's 1% chance you get 150 coins per block). - There is also 1/10,000 (0.01%) chance that a block will yield 1000 coins. This is valid for all 12 years of the mining. - The default ports are 9771 (connect) and 9772 (json rpc). Blockchain Explorers:http://jkc.cryptocoinexplorer.com/Pools1% POOL FEE Payoutsystem prop only 90 confirms dynamic Stratum 2-1024 Stratumport 3457 Getworkport 8457 http://coin-base.info/jkccoin/index.php
|
|
|
|
Bitcoin might currently be getting the lion’s share of media attention, as far as digital currencies go. But it’s not the only form of electronic money being mined, traded and spent.
Let’s meet some of the other digital currencies making the rounds online:
http://www.coindesk.com/what-other-digital-currencies-are-there/A few misconceptions, but then again to those not intimately familiar with the Alt-coin community, you can see how some things could get confused.  |
|
|
|
WWW.COINDESK.COMJust started today and has several interesting stories on Bitcoin and crypto coins in general. I am not associated with the site, However I was interviewed in one of the articles, as where a few others many of us will know.
|
|
|
|
From Bitfloor website https://bitfloor.com/
I am sorry to announce that due to circumstances outside of our control BitFloor must cease all trading operations indefinitely. Unfortunately, our US bank account is scheduled to be closed and we can no longer provide the same level of USD deposits and withdrawals as we have in the past. As such, I have made the decision to halt operations and return all funds.
Over the next days we will be working with all clients to ensure that everyone receives their funds. Please be patient as we process your request.
- Roman
founder - bitfloor.com
Great, I just started using them again and they were working so well. Ahh, well. Here's to hoping that maybe I will get some of the BTC back that was being held due to the theft last year. |
|
|
|
Developers please note: https://bitcointalk.org/index.php?topic=152030.0And now a more elaborate explanation:
0.7 and older nodes use BDB for storing the blockchain databases. It seems this database has a limit on the size of the modification it can make atomically to the database. With the larger blocks of the past days, it seems to have triggered the limit. The result is that 0.7 (by default, it can be tweaked manually) will not accept "too large" blocks (we don't yet know what exactly causes it, but it is very likely caused by many transactions in the block). Specifically, block
000000000000015c50b165fcdd33556f8b44800c5298943ac70b112df480c023 (height=225430) with >1700 transactions.
However. 0.8 (which uses a different database system) has no such limit, and happily accepts the block. As the majority of the hash power was on 0.8, the longest chain ended up using this block, which is not accepted by older nodes.
The solution is to (for now) go back to the old chain, which has block 00000000000001c108384350f74090433e7fcf79a606b8e797f065b130575932 at height 225430.
|
|
|
|
I have seen the question of TRC and BTC addressing in a couple of threads. Both BTC and TRC use the same address version which means addresses on both chains are valid on the other chain. If you have the address in one chains wallet, you also have the private key to that address and you can use that key pair on the other chains wallet. I will demonstrate how to dump private keys and import them. You can also use a program called "vanitygen" to try and generate custom addresses. Using either the command line daemon or using the console in the GUI (QT) version of either the BTC or TRC client: Pick the address you want to use. If using the command line use [getaccountaddress <account name>] to acquire the address from account name if needed. getaccountaddress test
1K4QedomXZGvbhSFV5MDf3rkb376seeugU To extract the private key to the above address use the [dumpprivkey <address>] command. dumpprivkey 1K4QedomXZGvbhSFV5MDf3rkb376seeugU
L3PjkDLhzMuPFMu1oEyqyvergjRLSyc5YNVH1QGZg95jNNMUnFtv
Switch over to the client you want to import the address into. Use the [importprivkey <privatekey> [label] ]. Label is optional but using it to name accounts makes life much easier when using the command line version. After running the command, the client will not give any feedback (older client versions would actually give a fake error message). importprivkey L3PjkDLhzMuPFMu1oEyqyvergjRLSyc5YNVH1QGZg95jNNMUnFtv Thats it, you should now have the use of the same address in both chains. If not using the GUI version you can list addresses with [getaccountaddress <account> ] getaccountaddress test
1K4QedomXZGvbhSFV5MDf3rkb376seeugU Vanitygen is located at: https://github.com/samr7/vanitygen.gitAfter installing vanitygen you can import the private keys it generates to use your own custom addresses. One little talked about option with vanitygen is the ability to use different address versions in order to generate addresses for other chains. For example: PPC address version is 55 (Decimal). Using the -X switch I can generate PPC addresses. vanitygen -X 55 PP123
Difficulty: 4553521
Pattern: PP123
Address: PP123ejYoxefhZkCT1tUgRvMkAT3VgfNT4
Privkey: 79eBxBYKymHAQBxnu3nz98CTLRUSKThvuzyUX2L6yt5D5Ci1xb2
ADD: The Base58.h file will need to be patched and PPCoin recompiled to import private keysDo not forget about oclvanitygen, it allows you to use your GPU to generate addresses. Note: All addresses and keys used in this post were made on fresh wallets and deleted afterwards. DO NOT USE any of the address or keys in this post as the pairs are now public information. |
|
|
|
|
