Show Posts
|
|
Pages: « 1 [2] 3 4 5 »
|
|
0.00000300 per coin
PM me if you have that amount
|
|
|
|
|
Will buy Fetish @ 0.00000300
Will buy from 1,000 to 50,000 (improbable)
Will take BDSM @ 0.00000030
Will do 100,000 to 700,000
If you've multimining at iSpace ,,,
|
|
|
|
|
Will buy Fetish @ 0.00000300
Will buy from 1,000 to 50,000 (improbable)
Will take BDSM @ 0.00000030
Will do 100,000 to 700,000
If you've multimining at iSpace ,,,
|
|
|
|
hello, https://github.com/CallMeJake/BlockCrawlerdoes anyone know if it is possible to put an rpc call to search by address in Block_Crawler? He put a block on lots of calls. If it is, I guess I would need to put something in block_crawler.php to reflect the new feature. Big ask of you, so apologies. bc_api.phpforbids things, but I want to make it so transactions would show by address (more user friendly) ---- // Enable the wallet require_once ("bc_daemon.php"); // A check for no request if (!isset ($_REQUEST["request"]) || $_REQUEST["request"] == "") { bcapi_error (0, "No Request"); } // URL formatting is stripped from the request $request = urldecode ($_REQUEST["request"]); // The request is split in case anyone tries to send a multi-parameter // request to the API, any parameters after method will be ignored $request = explode (" ", $request); // These are security checks to ensure that no one uses the API // to request balance data or mess up the wallet. if ($request[0] == "getbalance") { bcapi_error (1, "Method Not Permitted: getbalance"); } if ($request[0] == "listaccounts") { bcapi_error (2, "Method Not Permitted: listaccounts"); } if ($request[0] == "listtransactions") { bcapi_error (3, "Method Not Permitted: listtransactions"); } if ($request[0] == "keypoolrefill") { bcapi_error (4, "Method Not Permitted: keypoolrefill"); } if ($request[0] == "getpeerinfo") { bcapi_error (5, "Method Not Permitted: getpeerinfo"); } if ($request[0] == "listreceivedbyaddress") { bcapi_error (7, "Method Not Permitted: listreceivedbyaddress"); } // Check to stop remote users from killing the daemon via API if ($request[0] == "stop") { bcapi_error (6, "Method Not Permitted: stop"); } // The first word of the request is passed to the daemon as a // JSON-RPC method $query["method"] = $request[0]; // The data is fetched from the wallet $result = wallet_fetch ($query); // The wallet fetch routine has removed the JSON formatting for // internal use. The JSON format is re-applied for the the feed print_r (json_encode ($result)); // That's it. exit; // this function is here to generate repetitive error messages function bcapi_error ($code, $message) { $error["code"] = $code; $error["message"] = $message; print_r (json_encode($error)); exit; } ?>
|
|
|
|
|
I'm confused, any help will be appreciated.
There seems to be the view that you stick in a checkpoint every now and again (is it really necessary?)
SHA256 checkpoints.cpp says
// What makes a good checkpoint block? // + Is surrounded by blocks with reasonable timestamps // (no blocks before with a timestamp after, none after with // timestamp before) // + Contains no strange transactions So I map some checkpoints
( 0, uint256("0x00000447468db4b26ca942c2c6c700b49907e9d0d8ca6ce2bd84223a74972259")) ( 5000, uint256("0x00000000001070b052725af8bf364b9442f957347aa5344304c5c031dd373253")) ( 15000, uint256("0x000000000003d26b8091f8220f151218bb56fcb648ca70bb92968b83ac469848")) ( 25000, uint256("0x000000000004b042f2f61bea4a20d5e8823361d9615e352e34c8ea9b66b3a955"))
But what about the timestamp mentioned above?
Do I have to change the UNIX timestamp everytime I put a checkpoint in? So it matches the checkpoint, or do I just use the original?
My last checkpoint was 000000000004b042f2f61bea4a20d5e8823361d9615e352e34c8ea9b66b3a955 This corresponded with 1412731053 Timestamp
So do I change the timestamp?
static const CCheckpointData data = { &mapCheckpoints, 1412731053 // * UNIX timestamp of last checkpoint block
Or leave it as the original?
static const CCheckpointData data = { &mapCheckpoints, 1410084058 // * UNIX timestamp of last checkpoint block
And WTF to this? 1, // * total number of transactions between genesis and last checkpoint
Do I just add up the number (say it is 30,000), and put that in?
I known these are shitty questions that will make people groan, but I can't find the answers on Google.
Anyone?
|
|
|
|
|
Anyone intersted?
Not much being offered but will brand youi
5-6 LTCs.
|
|
|
|
|
Anyone starting a book on these?
I'm interested in trading, but want to see the general response to prices.
Some must be holding a lot, so something must be happening?
|
|
|
|
|
If anyone is interested in setting up both of either of these on another person's server (not mine), no frills, PM me.
Can negotiate a slice of takings for you. I am taking about a cryptsy coin, with bags of potential.
This should be win-win if you are skilled enough to make either of them quickly.
The competition is very poor, and has no support from the dev.
If you are interested you get promoted from the official site.
The gamble is spending 3 hours making a new pool and simplisitc game. The return will e good, of that I am sure.
NB i am not on a retainer, and I will not profit. The devs are honest and nice, which is why I am trying to promte them.
|
|
|
|
|
The Monero shill boys, taking breaks between school or looking after their mums, have been rather vocal.
But I suspect the price hit a week or two ago was the height of Monero's promise.
This will be a dirty sell off, and expect the duped punters to throw it all away after it drops another 25%.
Dead Coin Walking.
Funny thing is, all the fuss made, yet nobody apart from a handful of people even knew how to use the wallet (64 bit only, and no promises that it will work).
Oh dear.
|
|
|
|
|
I would appreciate a response to this. does anyone know how to remove the function getnetworkhashps?
Basically, so it does not appear on the Crawler.
I've tried doing it, but I seem to slice off the right hand side of the Crawler, so get no information.
The reason I am asking is I do not have that function as an rpc call, so it just shows up as "error", which looks pretty stupid.
Sorry to post the whole file, but if anyone answers, it might be that they spot it right away without ever having used the BC
____________
<?php
require_once ("bc_daemon.php"); require_once ("bc_layout.php"); // If a block hash was provided the block detail is shown if (isset ($_REQUEST["block_hash"])) { site_header ("Block Detail Page"); block_detail ($_REQUEST["block_hash"], TRUE); } // If a block height is provided the block detail is shown elseif (isset ($_REQUEST["block_height"])) { site_header ("Block Detail Page"); block_detail ($_REQUEST["block_height"]); } // If a TXid was provided the TX Detail is shown elseif (isset ($_REQUEST["transaction"])) { site_header ("Transaction Detail Page"); tx_detail ($_REQUEST["transaction"]); } // If there were no request parameters the menu is shown else { site_header ("Block Crawler Home Page"); echo " <div id=\"node_info\">\n"; echo "\n"; $network_info = getinfo (); echo " <div class=\"node_detail\">\n"; echo " <span class=\"node_desc\">Block Count:</span><br>\n"; echo " ".$network_info["blocks"]."\n"; echo " </div>\n"; echo "\n";
echo " <div class=\"node_detail\">\n"; echo " <span class=\"node_desc\">Difficulty:</span><br>\n"; echo " ".$network_info["difficulty"]."\n"; echo " </div>\n"; echo "\n";
echo " <div class=\"node_detail\">\n"; echo " <span class=\"node_desc\">Connections:</span><br>\n"; echo " ".$network_info["connections"]."\n"; echo " </div>\n"; echo "\n";
$net_speed = getnetworkhashps (); if ($net_speed != "") { echo " <div class=\"node_detail\">\n"; echo " <span class=\"node_desc\">Network H/s:</span><br>\n"; echo " ".$net_speed."\n"; echo " </div>\n"; echo "\n"; } echo " </div>\n"; echo "\n";
echo " <div id=\"site_menu\">\n"; echo "\n"; echo " <div class=\"menu_item\">\n"; echo " <span class=\"menu_desc\">Enter a Block Index / Height</span><br>\n"; echo " <form action=\"".$_SERVER["PHP_SELF"]."\" method=\"post\">\n"; echo " <input type=\"text\" name=\"block_height\" size=\"40\">\n"; echo " <input type=\"submit\" name=\"submit\" value=\"Jump To Block\">\n"; echo " </form>\n"; echo " </div>\n"; echo "\n";
echo " <div class=\"menu_item\">\n"; echo " <span class=\"menu_desc\">Enter A Block Hash</span><br>\n"; echo " <form action=\"".$_SERVER["PHP_SELF"]."\" method=\"post\">\n"; echo " <input type=\"text\" name=\"block_hash\" size=\"40\">\n"; echo " <input type=\"submit\" name=\"submit\" value=\"Jump To Block\">\n"; echo " </form>\n"; echo " </div>\n"; echo "\n";
echo " <div class=\"menu_item\">\n"; echo " <span class=\"menu_desc\">Enter A Transaction ID</span><br>\n"; echo " <form action=\"".$_SERVER["PHP_SELF"]."\" method=\"post\">\n"; echo " <input type=\"text\" name=\"transaction\" size=\"40\">\n"; echo " <input type=\"submit\" name=\"submit\" value=\"Jump To TX\">\n"; echo " </form>\n"; echo " </div>\n"; echo "\n";
echo " </div>\n"; echo "\n"; } site_footer ();
|
|
|
|
Open source and secrecy, it kind of clashes, so best to delete posts from your XMR self-moderated threads.  
|
|
|
|
|
Big sells today, whatever will happen?
|
|
|
|
|
A pile of junk coin, that has made its position by somehow replacing LTC as the second coin to trade on Poloniex.
It has features, though, but sadly the features are pointless, and can never go beyond appealing to teenagers and unmarried men in their thirties that have prostituted themselves to become Monero Shills. OMFG!
Horrible coin.
|
|
|
|
|
Impossible to be certain, given the amount of alts, and the change in the crypto culture.
My guess is 0.03 is on the cards, and within 2 weeks.
|
|
|
|
|
It appears to me, and someone can object if he or she has figures, that Xcoins are the bigest losers in this dump. I suspect the minor ones to disapear, and perhaps DRK will tread water for a while. Monero will cease to exist, surely.
BTC will probably spring back, which means LTC will probably follow.
The scrypt coins are currently fighting the idea that Asic means death. I have no idea why that would be the case.
Hardware upgrades all the time. This is a just a shift from GPU to Asic, and not everyone will have the Asic that can sweep up every coin.
More likely is that anything that can only be mined with a CPU is the one to fall.
So BTC, LTC, maybe DRK, perhaps NMC, PPC the only coins that could rebound for a period of more than a month.
DRK is the one I'm undecided on
|
|
|
|
|
this is how it will play out over the next month.
BTC always crashes, no reason why it won't go down to sub 200.
Xcoins are the new scrypt. Far too many, and the obsession with secrecy and PoS is not a selling point.
Nobody wants either apart from fantasists and the deluded.
So that leaves ... maybe DRK the sole survivor in terms of at least being traded (before it becomes XPM, Feathercoin, et al)
So back to business as normal; BTC, LTC, BTC, LTC, BTC, LTC.
Like the old days (of 8 months ago)
|
|
|
|
|
Effectively it is Ripple, even to the point where you don't get coins if you are entitled to them.
Mark my words, this will fail, just look at the team.
I never really thought of XRP as a scam, because I appreciated the attempt made. It was a great idea.
But this is just cashing in on the poor management of the Ripple experiment.
I don't personally think most coins are scamcoins, although they have increased lately.
I'm calling this a scam, a pompous, "aren't we wonderful," scam.
|
|
|
|
|
Looks like we're going there, and then what? a pump to 4 sats before it goes to LTC only?
Am I way off?
I have a feeling that we'll see a huge clearout at all the exchanges, Doge will survive, but as the low-end coin.
|
|
|
|
|