BitKey™ is going to be an secondary channel for transactions. The idea behind it is that an anoymous transaction
won't be an transaction which is traceable through the blockchain. Example: you want to transfer 100 ROOT from A to B.
Client A will automatically transfer the coins to an public address and then send it's encrypted private key with the
100 ROOTs to client B. Finally client B will have received the coins from client A without making an real transaction.
Users will be "identified" through a public key and a boradcasted RootCash-index with all clients/keys.
There's one thing I don't understand: Who chooses to which public address the coins are sent? How can you assure (or can you even assure) that client B is the only one who has the private key of this address. Because if not, client B would have to transfer the coins to a new address to make sure they really "belong to him" and therefore transaction fees would be charged two times. Please correct me if I'm wrong. please read the whitepaper as it explains the tx-mechanism which is used here more detailed. (there are NO tx-fees used for BitKey-transactions) to your question regarding the public key redundandce: keep in mind that the BitKey-IDs of each client are representations of an secp256r ECDSA keypairs public key. so there is no need to worry about somebody to generate the same priv-key. (with actual resource-limit not possible) |
|
|
|
I think sha-256 produces a smaller community than more CPU/GPU friendly algos.
I'm Glad to invest in a fresh coin with a solid dev.
thanks for the feedback. i ll count one vote towards scrypt for you. (or do you evtl. prefer x11/x13??) |
|
|
|
SHA256 OR SCRYPT?  Self moderated.  sure. sick of shitty posts.. and def. not going to put loads of work into something i am not able to protect like i want to protect. |
|
|
|
you have good plan for this coin....
of course... |
|
|
|
dev-progress: 2016: new dev team to be announced dev-progress: Fri 02/01/2015: New droid-app going online shortly - thanks to Youplab! dev-progress: Tue 30/12/2014: librootcoin released - special thanks to S4n! dev-progress: Mon 22/12/2014: Ostabiz & Youplab are now part of the dev-team! dev-progress: sun 21/12/2014: rootcoin.co new website online. check it out! TEAM
Collegestudent: community-manager & special supporter
Youplab: CO-DEV
Ostabiz: CO-DEV
CECVW: special supporter
enunrom: special supporter
Pools
[PoW is over!]
ROOT burn-address: R9HC5WtHbpoa51NCUAz86XLCmGTbkf45NT
Wallet/Source v2.0 | |  |  |  sample config-file:rpcuser=username
rpcpassword=password
listen=1
server=1
rpcallowip=localhost
addnode=192.99.223.96
addnode=198.23.160.13
addnode=212.91.189.164
addnode=195.34.100.2
addnode=94.156.237.70
roadmap for end 2014 - jan 2015
#RootCoin v2.0 changelog: gui-tweaks and extension of functionality (TBA)
#RootCoin v3.0 changelog: integrated mixing functionality and minimization
of tx-fee.
#BitKey v2 changelog: extended communication layer and rootEX-integration
for absolute anonymity.
I am announcing my cryptocurrency project named "RootCoin" [ROOT]. This is just an (my) economic/technical project/experiment.
Please inform yourself about cryptocurrencies and their risks before making any investment (money, time, hashingpower,..).
All sales are final!
RootCoin is in final development stage. This is my first own cryptocurrency-project and
i am going to do this as a fulltimeproject by myself. I ve been involved in a couple of altcoins and
also did/am doing a lot of contract based work within the cryptocommunity.
IRC: #rootcoin
Chinese QQ Group: 310988665
RootCoin will be an oldschool scrypt PoW/PoS/PoI coin with a 4-stage-distribution model:
Stage 1: Proof of Investment (Initial coin offering -> crowd fund)
Stage 2: pure PoW -> first 10 days will be pure PoW
Stage 3: hybrid PoW/PoS -> 2 weeks will be a hybrid PoW/PoS stage
Stage 4: 10+ PoS -> after that the PoS system will be generating blocks for +10 years (total of 68,950 ROOT will be generated with PoS in first year)
Specifications:
algorithm: scrypt (community voting)
blockreward: 99 ROOT
total coins: 3 million coins
blocktime: 5 minutes
PoS reward: 3%
rpcport: 27377
p2pport:28388
qrcode support
POW-CUTOFF: block 3700
+100 blocks were instamined at the offical pool.
about 380 blocks were instamined through solominers AFTER launch
and before the official pool started hashing. thats a total of 38k ROOT.
The codebase of ROOT was fork from another scrypt-coin
and the GetNextTargetRequired(), the function which settles the difficully,
reset the first 450 blocks with the starting diff. leading the first 450 blocks
to be mined superfast. - as this was topic for some FUD/troll posts, i just
added it to the OP to make it public.
ROOTCOIN-distributionThe final specification is: 53% ICO, 12.21% PoW and 34.79% PoSLaunch: On the launchdate ROOT will be ready with wallets for OSX, LINUX, WINDOWS. ANDROID coming soon. Blockexplorer and official mining-pool will also be provided at launch.
economical feature: BurnPool™
BurnPool™ will be a new kind of multipool. Users will be able to choose between two mining-options.
First option will be payout in RootCoins. Second and NEW option will be to multimine RootCoins
which get "burned" automatically by transferring them to an "proofen unspendable" public-key.
So with this step coins get burned, the coincap minimized and the value higher.
BOUNTIES:
Translations: 0.01 BTC per translation (translation has to meet our basic requirements)
baby222 - chinese
Yza_azY - italian
majningmaster - french
majningmaster - polish
Articles: 0.02 BTC per article (article has to meet our basic requirements)
future plans:
TBA
|
|
|
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, i confirm the arrival of 50% prepayment on my BTC-addr and will now start to fullfill the contract which includes the following work: +implementation of anon-tx system +rotate ALL key-pairs +gui-tweaks +updated sourcecode +whitepaper the anon-tx implementation i am going to use was designed by me & nik0lay and coded by me. please check my whitepaper for further details on the used technology: https://www.dropbox.com/s/m5nop0ev0jn16t6/whitepaper.pdfhttps://mega.co.nz/#!ecgklSaD!Eqkq5ny5NF6aQYlh0z1bLDDi0KOWug97mM71P_q62i8once the implementation is finsihed i ll post new sources and documentation. Github-repo ownership and privatekeys (alert , checkpoit-signing) will be handed over once final payment is transferred. regards, bitsta -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.25 (FreeBSD) iQEcBAEBAgAGBQJT1r2sAAoJEMmvoAYnC0ImrvwH/2r8lGw4He0jaMuZbSMVzOcJ bsEnfBKXeiMKVfcEHglYGgiJHFa5vPt0jTybPMWhJ+kr9iiXB3Ze0qbTghFyCNuI 61sjU9BROs4+GYY/qF2/ymavFItW+7kdF5bZbkuMXCh9cWMJjU10G9VkSkSa5jxz fWyHjycEADX+3Hc0Vf7OhriyOI1aNXyOzNcPJAlV45KPFnFu0uaIldzeTL568Ij5 YjymgWbLnhkj4pg5V72NLwFv3Jzv2IE7kDuvNdKc4CoUGZ7AI3ySXmQh+HStM4ga c6cUJmosIB7dt+EAmLFWdf+xliT/1+fk+pmCivsKVU8T87TuV7azS/PbdrqF7ng= =3rih -----END PGP SIGNATURE----- |
|
|
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, i confirm the arrival of 50% prepayment on my BTC-addr and will now start to fullfill the contract which includes the following work: +implementation of anon-tx system +rotate ALL key-pairs +gui-tweaks +updated sourcecode +whitepaper the anon-tx implementation i am going to use was designed by me & nik0lay and coded by me. please check my whitepaper for further details on the used technology: https://www.dropbox.com/s/m5nop0ev0jn16t6/whitepaper.pdfhttps://mega.co.nz/#!ecgklSaD!Eqkq5ny5NF6aQYlh0z1bLDDi0KOWug97mM71P_q62i8once the implementation is finsihed i ll post new sources and documentation. Github-repo ownership and privatekeys (alert , checkpoit-signing) will be handed over once final payment is transferred. regards, bitsta -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.25 (FreeBSD) iQEcBAEBAgAGBQJT1r2sAAoJEMmvoAYnC0ImrvwH/2r8lGw4He0jaMuZbSMVzOcJ bsEnfBKXeiMKVfcEHglYGgiJHFa5vPt0jTybPMWhJ+kr9iiXB3Ze0qbTghFyCNuI 61sjU9BROs4+GYY/qF2/ymavFItW+7kdF5bZbkuMXCh9cWMJjU10G9VkSkSa5jxz fWyHjycEADX+3Hc0Vf7OhriyOI1aNXyOzNcPJAlV45KPFnFu0uaIldzeTL568Ij5 YjymgWbLnhkj4pg5V72NLwFv3Jzv2IE7kDuvNdKc4CoUGZ7AI3ySXmQh+HStM4ga c6cUJmosIB7dt+EAmLFWdf+xliT/1+fk+pmCivsKVU8T87TuV7azS/PbdrqF7ng= =3rih -----END PGP SIGNATURE----- |
|
|
|
Well there was some miscommunication in escrow request pm, So I would like to get an confirmation publicly. Somekindabitcoin asked me to provide escrow on these terms. We just need you to hold 3 btc of funds that will be paid to him after his work is done.
Now If you guys want me to release bitcoins to dev in advance, I will do that as per users request, but I would like to mention that "escrow contract" will be terminated and I won't be responsible for anything once coins are released. @Bitsta Please provide your bitcoin address here. -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 my BTC address is: 1M33GAfdeiJfVZWjLbHoQ5DvCHB9cFBByx regards, bitsta -----BEGIN PGP SIGNATURE----- iQEcBAEBAgAGBQJT1qnDAAoJEMmvoAYnC0Imu6gH/ie269WAEI4HpJq/01qBIFUk E+2KxFVrh+wRaFTpEWJiNJu0Yn7UJSlTyLeYMiasQbo6H4Fo4/JV7FWgJY2zNKOA trBF9sx1ZDGY2lF2g6kQYFZcLnPfR2JTcE5OGVDERAGzFvd+0W3SivKhjoEBbYB0 JUnwPBaaV0McODctOxlhH7gcE/YI2+7zQBcFyqzpFmy5oQx4BaDzsjVU9D3B7NuC hxfvIpHXazYqnXbOy9p3A7TD+A0z78YVOUzslCOW6U3+FpOlzGlx17xy0OsDfxrz Am7mHKH53JZLmdivInVuUVDPrkaF0lw2hUS6Jw23tberfJnD4toxwTgWj0iM4NY= =UFJz -----END PGP SIGNATURE----- |
|
|
|
When I use the command "listsinceblock" in bitcoind I get some weird looking data for a multisig address. Can anybody explain this to me? Lookng at the txid, we can see that the two listed transactions represent the same transaction. Is this a bug in Bitcoin Core? The list for single signature addresses look correct. The multisig address should only have one incoming transaction and no outgoing transactions as can be seen on blockchain.info: https://blockchain.info/address/34N5MSC3brnr183yRBBQYFRYNVmGf1ymhw
sirius@sirius-ThinkPad-Edge-E540 ~/Documents/bitcoin-0.9.2.1-linux/bin/64 $ ./bitcoind listsinceblock
{
"transactions" : [
{
"account" : "",
"address" : "34N5MSC3brnr183yRBBQYFRYNVmGf1ymhw",
"category" : "send",
"amount" : -0.00990000,
"fee" : -0.00010000,
"confirmations" : 13,
"blockhash" : "0000000000000000064594fd44816f8ab656d2f2627848990c47f791e4276ad4",
"blockindex" : 131,
"blocktime" : 1405007016,
"txid" : "7850528d3b57e3993d56b4f7cd90198fe3a329a4045bb240737758c6fb554b94",
"walletconflicts" : [
],
"time" : 1405006463,
"timereceived" : 1405006463
},
{
"account" : "",
"address" : "34N5MSC3brnr183yRBBQYFRYNVmGf1ymhw",
"category" : "receive",
"amount" : 0.00990000,
"confirmations" : 13,
"blockhash" : "0000000000000000064594fd44816f8ab656d2f2627848990c47f791e4276ad4",
"blockindex" : 131,
"blocktime" : 1405007016,
"txid" : "7850528d3b57e3993d56b4f7cd90198fe3a329a4045bb240737758c6fb554b94",
"walletconflicts" : [
],
"time" : 1405006463,
"timereceived" : 1405006463
},
please try to use it with proper parameters/arguments. listsinceblock [blockhash] [target-confirmations] example: ./bitcoind -listsinceblock 0000000000000000365692b410bf843d6f7b7e0959c064f959776114e908fa8d (this should list your tx as it s the previous block before your tx was made) taken from the API list: API description of "listsinceblock [blockhash] [target-confirmations]": Get all transactions in blocks since block [blockhash], or all transactions if omitted. [target-confirmations] intentionally does not affect the list of returned transactions, but only affects the returned "lastblock" value. |
|
|
|
Hi  I'm creating an ASP.NET website in c#. I want to allow a registered user to create his own bitcoin wallet in the website in which he will be able to deposit and withdraw bitcoins to an external wallet. I have experience with ASP.NET and C# but i am pretty new the crypto world. I've heard about libraries like BitcoinLib and BitcoinSharp but i wasn't able to find a good documentation that would explain to a newbie like me how to create a wallet in my website. I also tried to use the blockchain.info api but it takes too much to complete a transaction and i have heard some bad comments about that api. Also, i don't feel comfortable with relying on a third party api. I would really appreciate if someone would give me or address me to a proper explanation of how i can implement such system in my website. Thank you very much hi, first you should check some basic stuff: https://en.bitcoin.it/wiki/Original_Bitcoin_client/API_Calls_listthanks god we have json-rpc which can be used for wallet-communication. so C# offers two basic options for this realization: 1. use standard http json reqests. EXAMPLE: (C#) if you use http s JSON-RPC calls (SSL --> see "rpcssl") PLEASE MAKE SURE TO HAVE ACTUAL OPENSSL VERSION INSTALLED! HttpWebRequest webRequest = (HttpWebRequest)WebRequest.Create("http://localhost.:8332");
webRequest.Credentials = new NetworkCredential("user", "pwd");
/// important, otherwise the service can't desirialse your request properly
webRequest.ContentType = "application/json-rpc";
webRequest.Method = "POST";
JObject joe = new JObject();
joe.Add(new JProperty("jsonrpc", "1.0"));
joe.Add(new JProperty("id", "1"));
joe.Add(new JProperty("method", Method));
// params is a collection values which the method requires..
if (Params.Keys.Count == 0)
{
joe.Add(new JProperty("params", new JArray()));
}
else
{
JArray props = new JArray();
// add the props in the reverse order!
for (int i = Params.Keys.Count - 1; i >= 0; i--)
{
.... // add the params
}
joe.Add(new JProperty("params", props));
}
// serialize json for the request
string s = JsonConvert.SerializeObject(joe);
byte[] byteArray = Encoding.UTF8.GetBytes(s);
webRequest.ContentLength = byteArray.Length;
Stream dataStream = webRequest.GetRequestStream();
dataStream.Write(byteArray, 0, byteArray.Length);
dataStream.Close();
WebResponse webResponse = webRequest.GetResponse();
... // deserialze the responsethe 2. option is json.Net ( http://james.newtonking.com/json ) which is a high performance JSON package for .Net cheers, bitsta |
|
|
|
I found on another thread a reference to a RPC command "importwallet" although i can find no documentation about it anywhere so i am looking for a different approach.
How would a person import a list of private keys into Bitcoin QT through either debug window or Bitcoind? Not a single address but a long list of private keys.
write a script (python, perl, bash) and use a loop which executes the rpc-command "importprivkey" on every privatekey inside your list (list could be realized with loading an external file[containing the privkeys] into an array). if you need any support, let me know. regards |
|
|
|
i still use bitcoin-qt 0.8.x
i was wondering if i MUST upgrade in the near future to be compatible with the rest of the network.
is their an end date when everyone needs to be using 0.9.x or will 0.8.x last me for a good while ?
i just prefer the layout of 0.8.x before anyone asks why i do not upgrade =)
and yeah i no it might be vulnerable to heartbleed but i do not use rpc which i believe would make me not vulnerable ?
thanks happy people!
your client will be dropped from the network once the actual version gets a new minimum protocol version. the actual min protocol version is: 209. this is hardcoded into version.h ( https://github.com/bitcoin/bitcoin/blob/master/src/version.h#L35). so lets say you have a client with protocol version 210. the actual p2p network will accept your node as the min. protocol version is 209. now let s say that the min. protocol version gets updated to 211 for some reason. your client will now be disconnected from all updated clients as thy won't accept your minimum protocol version. and as for the OpenSSL bug. YES you are theoretically vulnerable as long as you use the old OpenSSL version. the bitcoin protocol itself is secure and not affected by the heartbleed bug. but in fact your computer is unsecure as long as that version is running. and as long as your computer is not safe, you bitcoins are either.. so a dedicated hacker would be able to get access to your machine and steal your coins without even touching the wallet/rpc.... (keylog + wallet.dat: just to mention ONE method..) SO PLEASE UPDATE YOUR OPENSSL (if you haven't done yet) AND ROTATE ALL YOUR SSL KEYS!!! regards, bitsta |
|
|
|
.
BTC improvement proposal 10 describes a way to standardize the encoding of proposal transactions, to assist with signature collection and broadcast (which includes regular, 1-of-1 transactions requiring signatures from an offline computer). The goal is to encourage a standard that guarantees interoperability of all programs that implement it. [source: https://github.com/bitcoin/bips/blob/master/bip-0010.mediawiki] check the link posted above. hope this helps. cheers, bitsta |
|
|
|
Looked through the changelogs and couldn't really see anything, except one mention that RPC calls would be separated from bitcoind sometime in the future. Anyway, has there been a chance recently (ie. v0.9.2+) in the startup process? Previously, I would just run "bitcoind -daemon", and all would hum along just fine.
Now though, that doesn't seem to work, because if I kill that SSH connection, things like "blocknotify" seem to stop working. I've resolved this with using "nohup bitcoind -daemon &", and that seems to keep it going just fine even after the SSH session. Just curious, has anything changed in that regards, and is there anything else I should be aware of?
Thanks!
not that i know. have you launched the daemon inside a new screen-session? |
|
|
|
This was easily one of the best threads to read up on and post in, there was no bickering, now things have taken a turn it seems.
Can we quit arguing and get back to figuring out this whole POS transition and more?
"We"? who, the community? This is BK's coin. And BK has hired "Bitsa" to be the dev of the POS. Now, BK is a veteran of crypto and NAUT is supposed to be the fruit of all that experience. Initially, if I have it correct, NAUT was not going to be POS but now BK has decided that it will be (feel free to correct me when I am in error, please). And now, after the coin has lost between half and 2/3s of its value of earlier today, are we, the community, supposed to cook out the "transition and more"? OK... I'll add the little that I know: "Bitsa" seems to be a "for hire" developer that apparently was rejected by Gatti and Shogun47 in their botched attempt to get Libertycoin away from Carlor Torres Ferguson, the Mexican scam dev of Libertycoin -and many others scam coins-. Apparently, "Bitsa" didn't know how to operate the coin in practical terms for the attempt was only that, a failed attempt. And, ultimately, he just wanted money. Which is quite legitimate when you work and are capable of doing the job you are hired to do. It seems BK has deemed "Bitsa" capable of doing not just the "transition" but to actually be the dev of the POS part of NAUT. And BK should know, doesn't he? So we, the community, are suppose to "figure out" something? It looks to me that we are left with two very clear options: Either remain invested in NAUT and hope it rebounds and diminishes with it the losses OR we may cut those and just leave. But that is just me thinking, of course. hi barabbas, i just want to make something clear. i ve worked for shogun47 (@XLB) thats right. and i HAVE FULLY FULLFILLED MY contract. I VE MADE WHAT I WAS TOLD TO MAKE. (added an invalidation block into the sources, swapping all signing pub_keys, etc...) the failed attempt to get all users on that codebase was not part of the contract and therefor NEITHER MY FAULT NOR MY RESPONSIBILITY!!! as for PoS transition of NAUT: i won't ever release an unstable and potentially buggy PoS system. there are many reasons for that (reputation, lossrisk for users, etc.). we are acually working on the PoS for NAUT and adapting the stakemodifier like i stated in my earlier post. regards, bitsta |
|
|
|
|
@RAXE.IO : THANK YOU FOR THE PAYMENT! I just received the outstanding amount.
|
|
|
|
Guess, devs are just busy right now.
They obviously invested/investing money in development of this project. Would be wierd if they'd just go like "nnnah, fuck this shit, we're tired of coding and shit, we'll just let it die"
true.... but nothing been released after the wallet update.... ( i still dont got any stake yet...) Im still waiting for the IOS wallet... wich was gonna be released soon (you said that 2 weeks ago raxe.io) as it it is it seems the coins have to sit in the wallet for a bit over 7 days before stake begins.  now bitsta.. i agree with you. it is working ;p lol. i told you that. we tested it twice in an fresh network. so i would never go into a thread and post bold, red, alerts if i am not totally sure and tested it 100%. |
|
|
|
unus pro omnibus, omnes pro uno. Specification
Total Money Supply: 300 Million ShibeCoins
Proof of Stake Reward: 10% per year
Block Time: 60 seconds
Coin Maturity: 10 blocks
Confirms: 4 blocks Future Plans- shibesend™
- shibeBay
- shibeTV
- shibeADs
- shibeChat
|
|
|
|
i understand what he is saying tho. from a dev's point of view.. he has done good work and it will perform. but business doesnt really run like that. there needs to be visual confirmation..
i am sure raxe.io will pay you what you deserve bitsta.. but if you will forgive me.. i really did not appreciate that post im sure equally as much as u did not enjoy mine. we bury the hatchet now.. it was made out of plastic anyway and not sharpened steel ;p
+1 yeah, correct. let s move on and get things done. |
|
|
|
|
Show Posts
