Still need someone who can FIX (BOB) Dobbscoin. GITHUB
It no longer builds from source.. no one seems to know why.
I dunno why no one can get it working. I made the minor adjustments to get it compiling ~6 months ago https://github.com/Shinoa-Fores/dobbscoin-sourceGCC: 7.3.0 - None of the other deps changed. If anyone is trying to build this and fails, reply in this thread with a paste of your build log, or contact me on freenode irc in the #dobbscoin channel. I'll be glad to help you get it sorted. |
|
|
|
If you can relink me to the XJO telegram group and I'll bookmark it. I'm trying to get better at keeping records of what group is where  |
|
|
|
I sincerely hope Nova exchange is "back" with far better service than previously. The last iteration was a lulzfest, is there any reason to believe this isn't just another "Pay to list with us, thanks for the BTC, kthanx bye" as last time?  Hey, Shinohai! Cool to see you here. I have been following The Nova Thang all along. Gotta give these guys the benefit of the doubt: noo management. Hey, I'm ever the pessimist.  I still idle in the #dobbscoin irc chan. Been real quiet there, though BtcBob did pop in for a few minutes around the holidays. So no updates on the revival as of yet. |
|
|
|
I sincerely hope Nova exchange is "back" with far better service than previously. The last iteration was a lulzfest, is there any reason to believe this isn't just another "Pay to list with us, thanks for the BTC, kthanx bye" as last time? |
|
|
|
www.bittoilet.com has added UNO in it's shitcoin support section, though UNO is no shitcoin. What a lame begging site. |
|
|
|
I must say, I read one of Andrey123 posts in the BlackCoin thread and for me I also started to doubt when I saw Cyrillic characters (sorry) and a file hosted on Mega.
I just wanted to say the Cyrillic thing had nothing to do with my post - I work with a lot of Russian speaking individuals in Lisp communities on irc and telegram. Scammers can be found amongst any national group. Remember your wallet will default to the language used by your operating system in most cases. Previously, I saved it on Dropbox, but people asked me to save it on Mega.
And I thought it was a good option.
Do consider making a key, and then stake it in this thread . If you need assistance getting GPG set up I am more than happy to help, just message me. I am 1000% more likely to try one's code if it is at least signed, even if hosted on mega - though indeed there are more professional venues for such things. |
|
|
|
I have been geeking with Shinohai for YEARS. He enjoys the trust and support of all the members of our aliance. I will follow his advice on this issue.
I do not mind checks! Just install the Jesse operating system on your Rapsberry. Install dependencies and run the wallet. In there are no viruses, as I wrote above, the wallet is assembled from files downloaded from the GitHub coin developers. It's mostly advice to make you appear a bit more professional. To wit: 1. Why Mega? This is the #1 haven for bad actors. This should be hosted on shithub or gitlab at very least. 2. Strip your executable of debug symbols before uploading. This has the benefit of reducing size, which is a big consideration for RasPi and SBC users. 3. This is crypto. Get a GPG key and sign your work if you are proud of it, so we know "Yes, this is really Andrey123's work and not someone else impersonating him". At the very least, sha512sum the resulting bin so one can verify it hasn't been tampered with. 4. Without a key, you really don't exist in crypto. (See #3) It's admirable that you are producing things like this for those that are unable, and your binary did work for me in a sandbox with 0 problems. But in this day and age one simply cannot be too careful. |
|
|
|
Hello! I made a coin purse for the Rapsberry Pi 3 computer. And I will be very glad to coins 4GHbrGWoBpgi4599tdBKbSE4ix3s4uDyXM https://mega.nz/#!cjpWFAoY!1AEB-XW-pAOz7IJcMQrWTQoWZn2xN8cE7drN4DlwmaI I absolutely, 1000% DO NOT RECOMMEND anyone running an unsigned binary like this until someone has vetted it. Will take a look at it when I get a chance to run it on a sandboxed VM. |
|
|
|
I use CentOS 7, and have used Ubuntu before. I haven't had this issue at all, and recompiled to check again. I know I have somewhat been in contact with the issue before, but I can't remember thoroughly where. Newer version of Bitcoin source code have changed to full path, so probably others have encountered the same issue. By the way, if you wanna talk more interactively you can join the Joulecoin Discord channel: https://discord.gg/RaWB3uEAnd send me a private message.  In my experience, the issue only happens with newer g++ ( Currently building with 7.3.0 as 8.x.x will not build db4.8 without a patch, and I like consistency across coin builds). By a stroke of luck, I just got discord working in bitlbee/weechat yesterday. Will join at some point today. Thanks! |
|
|
|
This is awesum work as well! Feel free to message if I can be of any assistance, having insight API is a very important thing for developers. Already have a couple of ideas brewin and look forward to having the tx comments enabled. I have a bot skeleton on telegram that could definitely make use of this.
Finished up with the API and added some visual preferences, e.g. the arrow turns "blue" when there is a transaction message available; simply click on the transaction ID, and the message is there with all the other information. Here you can witness one of the first comments ever used: https://insight.joulecoin.info/block/000000000017ec018cc65d56d69d737f9da00b885c69a207b1b1219728502cdfThe API is available on: https://insight.joulecoin.info/apiI hope everyone using it will take it easy on my free services. Top notch work! I let IMZ know this was up, and I will likely use the API on my telegram bot, as I mentioned previously (But don't worry, abusers of bot services quickly get blacklisted and in our small group everyone s well behaved ). I have applied a couple of fixes to XJO sources, but for some reason shithub won't let me make pull request to main repo, as it hates when you have multiple sources of same project. This is mostly a simple change I applied because C++11 doesn't play nice with the main repo for whatever reason: https://github.com/Shinoa-Fores/joulecoin/commit/c2983f8d6a74fca82a7581dd34275e869d17a94cand https://github.com/Shinoa-Fores/joulecoin/commit/18116e0a6f436079fa9ee9f0b67b697d2beb292a (Because I forgot to push it the first day xD ) One or two other minor fixes listed there that may or may not affect others, I use Gentoo so these may not be a problem on other distros, haven't tested yet. |
|
|
|
The 10 first ones should not exist. They are already too greedy and, stopping adoption. Above 5000 UNO, you are a multi-national, technically, not a peasant.
Or not enough people will even use UNO. How, if only 10 guys have some?
You know.
It is not the man who has little, but he who desires more, that is poor. - Lucius Annaeus Seneca
|
|
|
|
Have been busy the last 2 weeks integrating Joulecoin into all insight libraries, and modifying the Bitcore client. After a lot of headaches I finally got it up and running, and have the last few days done some visual improvements. I'm planning to upload everything organized to GitHub, once I have cleaned it up more and fixed some other remaining things. Unfortunately I have not completely integrated transaction messages into the API. I know, but it will be fixed soon. It is far from complete (if it ever will be), but I feel I'm comfortable having it online now. For anyone wanting to take a look, Introducing: https://insight.joulecoin.info/This is awesum work as well! Feel free to message if I can be of any assistance, having insight API is a very important thing for developers. Already have a couple of ideas brewin and look forward to having the tx comments enabled. I have a bot skeleton on telegram that could definitely make use of this. |
|
|
|
I have been away a lot. Just checking back in and realized we never properly thanked you.  We lost hosting on the OLD Main Explorer, and have escolated you to MAIN EXPLORER Status. "BOB" Loves You! I've been away myself, but got to talking with IMZ about dobbscoin last night and got all nostalgic for it. He was having issues getting client to sync, so I decided to attempt a build on linux. I understand a revival of sorts may be going on, and there may be significant changes to the wallet but I managed a build with a few minor tweaks to the github repo: https://github.com/Shinoa-Fores/dobbscoin-sourceI am using: gcc version 7.3.0 (Gentoo Hardened 7.3.0 p1.0) with linux 4.15.4 kernel build. It all synced up fine, though I noticed only 1-2 peers. I will attempt to get a permanent node up to help the network this coming week. As I am also a big fan of paper wallets, I have put up a temporary generator at http://btcinfo.sdf.org/DLX/genwallet/?currency=dobbscoin# ... will also put the changes on github. The background is generic and doesn't have the groovy feel of the old version, so if anyone can improve please advise. |
|
|
|
If you run a service for $UNO (exchange or miner), check your #Unobtanium withdraw fees. We recommend .0001 Uno withdraw fee.
Many services set their fees when Uno was $1. It Uno routinely trades above $100. Please lower $UNO withdraw fees to reflect current realities.
To clarify, in your `unobtanium.conf` file simply add: or whatever amount you wish it set as. Adjust according to market conditions. Simple. |
|
|
|
Got six players in my outfit now trading 42 or going over the code.
Love 42? Run your wallet
o7 Thanks to Lasergun for all his hard work, and IMZ for the all-around support. After many trials and tribulations got a working 42 suite built from source on Gentoo. |
|
|
|
We are getting better:
encrypt a message. Run it through a paste bin. Send the URL as a tx comment.
Made a web page where it is possible to encrypt a message via AES encryption with a key. The compression ratio isn't perfect, but it increases to 67.4% before 240 character limit is reached. However website linking is an awesome way to save storage for the Blockchain. I got the following number for efficiency on the encryption compression ratio: 0.341 IN:15 OUT:44
0.484 IN:31 OUT:64
0.583 IN:63 OUT:108
0.617 IN:79 OUT:128
0.625 IN:95 OUT:152
0.645 IN:111 OUT:172
0.662 IN:143 OUT:216
0.674 IN:159 OUT:236 So at a small encryption it is around 35%, going all the way to ~67% at its best (maximum length encryption). Which provides an maximum input of 159 characters before encryption, resulting in a 236 character long hash. It's made possible with Javascript, so everything is happening local. GitHub: https://github.com/brix/crypto-js/tree/release-3.1.2I haven't made the first encrypted transaction message via the website yet. Probably will later. I had issues making clipboard button cross-browser compatibility with legacy support. So I have not missed this, I just wasn't happy with the current outcome. Regarding the possibility to download the web page and run on other machines which are not connected to the internet, is also something I have in the pipeline. Introducing: https://joulecoin.info/encrypt.html- Online AES encryption and decryption made in mind for Joulecoin transaction comments. Appears github is down this morning, but I will definitely check this out as soon as they come back up today and report back in. EDIT Finally was able to check it out, very nice work. Please keep us apprised of this and will gladly test with IMZ. |
|
|
|
We are getting better:
encrypt a message. Run it through a paste bin. Send the URL as a tx comment.
As you know, I've been working on a telegram bot for a few weeks now - a W.I.P. is being able to do this directly from our chat. As it sits, can already check price, network nodes, explore blockchain, etc. DLX - Membership has it's privileges. (tm)  |
|
|
|
Here is a list of nodes my telegram bot returns, appears there are still quite a few running old versions of the client: [
{
"subver": "/Satoshi:0.10.4.1/",
"protocol": 70003,
"nodes": [
"165.227.226.221",
"217.169.182.114",
"78.129.185.31"
]
},
{
"subver": "/Satoshi:0.10.4.2/",
"protocol": 70003,
"nodes": [
"108.170.1.134",
"121.215.18.43",
"140.0.53.177",
"158.174.16.27",
"173.249.20.203",
"173.249.34.241",
"176.31.255.29",
"176.31.53.107",
"176.9.25.79",
"178.128.200.126",
"183.195.46.116",
"185.28.249.80",
"188.165.235.208",
"188.241.58.126",
"192.99.19.133",
"194.158.201.106",
"194.19.235.71",
"194.32.77.32",
"195.201.10.19",
"198.27.81.114",
"208.94.242.218",
"213.147.177.64",
"213.148.193.153",
"217.175.119.125",
"23.111.174.246",
"31.0.122.153",
"37.45.166.189",
"45.33.22.9",
"46.23.35.70",
"5.189.186.124",
"62.210.177.156",
"62.210.180.148",
"71.206.73.12",
"74.124.24.228",
"75.164.231.159",
"75.169.62.203",
"77.249.213.25",
"77.37.209.233",
"77.95.36.184",
"79.173.118.160",
"79.72.225.171",
"79.72.227.250",
"80.218.217.199",
"85.14.242.77",
"86.177.207.136",
"86.99.172.188",
"88.22.208.79",
"92.35.81.84",
"94.130.16.85",
"98.116.109.15"
]
},
{
"subver": "/Satoshi:0.10.4/",
"protocol": 70003,
"nodes": [
"161.53.18.50",
"173.212.202.33",
"198.50.204.112",
"50.225.198.67"
]
},
{
"subver": "/Satoshi:0.9.2.4/",
"protocol": 70002,
"nodes": [
"91.121.221.92"
]
},
{
"subver": "/Satoshi:0.9.2.5/",
"protocol": 70002,
"nodes": [
"52.14.92.197"
]
},
{
"subver": "/Satoshi:0.9.2.6/",
"protocol": 70002,
"nodes": [
"188.134.72.213",
"24.61.14.159",
"5.127.79.43",
"63.247.147.166",
"97.93.182.237"
]
},
{
"subver": "/Satoshi:0.9.2.7/",
"protocol": 70002,
"nodes": [
"213.21.201.153"
]
},
{
"subver": "/Satoshi:0.9.2.8/",
"protocol": 70002,
"nodes": [
"162.251.150.125"
]
}
]
For now, I am simply blacklisting older versions that try to connect to my client. |
|
|
|
|
Show Posts
? IMZ!!!1 We like to stomp out any 42 impostors!!! 
