cinnamon_carter

DEVELOPER
  • Content count

    967
  • Joined

  • Last visited

  • Days Won

    6

cinnamon_carter last won the day on December 18 2013

cinnamon_carter had the most liked content!

1 Follower

About cinnamon_carter

  • Rank
    Developer of Cinnamon Coin, Photon, and.......

Contact Methods

Profile Information

  • Country
    United States
  • Location
    Philadelphia / Cyberspace / Twitter
  • Gender
    Female
  • Interests
    Several not limited to advanced math, science, technology, hacking, history, politics, philosophy, truth, art, AND OF COURSE CRYPTOCURRENCY ! Follow me on twitter at @cinnamon_carter , check out my coin @cinnamoncoin on twitter or here at the forum.

Recent Profile Visitors

1,982 profile views
  1. did you start with a new win 7 install on virtual box and then download and install the exact tools recommended in my 'update' ? as to the question is this thread maintained !! lol I am a busy woman, also for a while had issues signing into the forum here with crazy hard cloudflare captchas Not sure if Jimmy tweaked things or if cloudfflare did but lately i have been able to sign in easier , i suggest sending me a tweet on twitter if you worked on it as much as you can and retraced your steps Then normally within a few days or so depending on what else I have going on I can try to check the thread....
  2. suggest that you review this earlier post of mine and use a clean win 7 install on virtual box for best results https://cryptocointalk.com/topic/13204-how-to-build-a-windows-qt-wallet-for-any-coin-yourself-from-source-code-step-by-step-instructions/page-7#entry204544 also without being able to see the source code of what you are trying to compile , the pro file, knowing exactly what your toolchain is (specific versions ect...) i would find it very difficult to assist --- for example does your pro file have code in it to tell the compiler to ignore certain errors ? in the past ive seen this error at times, i know it is certainly possible to build a wallet with the error
  3. updated full guide for new version of photon --- 8.9.6 use virtual box and the necessary iso image to build a new windows 7 system (Strongly recommended) Install msys shell from here http://sourceforge.net/projects/mingw/files/Installer/mingw-get-setup.exe/download When you launch the installer check only after the initial install msysbase.bin Apply that and let the installer download the necessary files. Install this version of the mingw builds project toolchain http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win32/Personal%20Builds/mingw-builds/4.9.2/threads-posix/dwarf/i686-4.9.2-release-posix-dwarf-rt_v3-rev1.7z/download Use 7z to unpack it and put it on the root or c drive in a folder called mingw32 In the win 7 control pannel go to user accounts -- change user account settings--- pull the lever all the way down, setting it to never notify you when software makes changes to the system. Right click on 'mycomputer' and click properties, then click advanced system settings, and environment variables, carefully edit your Path put this first with a semicolen after it in front of what is allready there C:\mingw32\bin;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\ NOW ---------- unpack / place the following items to a folder on your c drive called 'deps' OpenSSL download open ssl 1.0.2e here https://www.openssl.org/source/openssl-1.0.2e.tar.gz open the folder C:\MinGW\msys\1.0\msys.bat and double click on the bat file to open a msy shell (a way of running a unix/linux type shell on win) cd /c/deps/ tar xvfz openssl-1.0.2e.tar.gz cd openssl-1.0.2e ./Configure no-zlib no-shared no-dso no-krb5 no-camellia no-capieng no-cast no-dtls1 no-gost no-gmp no-heartbeats no-idea no-jpake no-md2 no-mdc2 no-rc5 no-rdrand no-rfc3779 no-rsax no-sctp no-seed no-sha0 no-static_engine no-rc2 no-rc4 no-ssl2 no-ssl3 no-test mingw make depend make Next download Berkeley DB (version 4.8.30) http://download.oracle.com/berkeley-db/db-4.8.30.NC.tar.gz cd /c/deps/ tar xvfz db-4.8.30.NC.tar.gz cd db-4.8.30.NC/build_unix ../dist/configure --enable-mingw --enable-cxx --disable-shared --disable-replication make ===== download boost 1_55_0 from a msdos box with admin privliges --- you will put it together --- http://sourceforge.net/projects/boost/files/boost/1.55.0/boost_1_55_0.7z/download cd C:\deps\boost_1_55_0\ bootstrap.bat mingw b2 --build-type=complete --with-chrono --with-filesystem --with-program_options --with-system --with-thread toolset=gcc variant=release link=static threading=multi runtime-link=static stage -----miniupnpc-1.9.20150206----------- you build this also from dos box but unpack from msys command box one little trick is necessary here ---- download it here http://miniupnp.free.fr/files/download.php?file=miniupnpc-1.9.20150206.tar.gz from msys prompt tar xvfz miniupnpc-1.9.20150206.tar.gz change the folder in deps miniupnpc-1.9.20150206 to be named miniupnpc now from a dos prompt cd C:\deps\miniupnpc mingw32-make -f Makefile.mingw init upnpc-static *********note the trick is to copy everything inside this folder and make a new folder inside the folder cd C:\deps\miniupnpc called miniupnpc and copy everything from the C:\deps\miniupnpc to C:\deps\miniupnpc\miniupnpc ------------ next libpng and qrencode http://download.sourceforge.net/libpng/libpng-1.6.16.tar.gzand http://fukuchi.org/works/qrencode/qrencode-3.4.4.tar.gz now from a msys command prompt cd /c/deps/libpng-1.6.16 configure --disable-shared make cp .libs/libpng16.a .libs/libpng.a cd /c/deps/qrencode-3.4.4 LIBS="../libpng-1.6.16/.libs/libpng.a ../../mingw32/i686-w64-mingw32/lib/libz.a" \ png_CFLAGS="-I../libpng-1.6.16" \ png_LIBS="-L../libpng-1.6.16/.libs" \ configure --enable-static --disable-shared --without-tools make )))))) qt open source everywhere 4.8.6 http://download.qt-project.org/official_releases/qt/4.8/4.8.6/qt-everywhere-opensource-src-4.8.6.zip use 7z to put the contents of this zip file to a folder called c:\qt\4.8.6 cd C:\Qt\4.8.6 configure -release -opensource -confirm-license -static -no-sql-sqlite -no-qt3support -no-opengl -qt-zlib -no-gif -qt-libpng -qt-libmng -no-libtiff -qt-libjpeg -no-dsp -no-vcproj -no-openssl -no-dbus -no-phonon -no-phonon-backend -no-multimedia -no-audio-backend -no-webkit -no-script -no-scripttools -no-declarative -no-declarative-debug -qt-style-windows -qt-style-windowsxp -qt-style-windowsvista -no-style-plastique -no-style-cleanlooks -no-style-motif -no-style-cde -nomake demos -nomake examples mingw32-make -----------------go for a coffee this takes a while to build and even longer on a virtual machine --------------- get the source code of Photon from github at this point of the tree https://github.com/photonproject/photon/tree/2f10beca59449cec3a4592a92e90e088f314abac unpack it and place it in a folder called photon on your root drive in the photon-qt.pro file edit it with any basic text editing file as follows 'uncomment' (delete the # sign at the start of the line) line 35-47 78, 80,81 and 83 comment out line 145 NOW TO BUILD THE WALLET -- restart your virtual machine after you did all of the above ------ from a win command prompt cd C:\photon\ set PATH=%PATH%;C:\Qt\4.8.6\bin qmake "USE_QRCODE=1" "USE_UPNP=1" "USE_IPV6=1" photon-qt.pro mingw32-make -f Makefile.Release the wallet will be in the release folder of photon and ready to use happy new year // cc
  4. someone mentioned building a qt in linux , this is about 1000% easier than windows !! normally i build only the daemon for use on linux and the latest version of photon is optimized for using fewer resources on linux if anyone really needs direction on building anything in linux let me know and I may throw a short guide together and put it up. Chances are normally if you are using linux you likely dont use a qt wallet with the graphic user interface / Still I may be wrong.....
  5. If you are going to use this guide please pull / use the source code from this point in history https://github.com/photonproject/photon/tree/f8354b9a83fcf527d05ed01411198b3544453965 since with the most recent release our team has 'changed' a few things and the commands/tools used to build the wallet are not the same they used to be. for example, we are now using mgw 492 or 493 , this guide used mgw 464 Best advice i have to anyone to build anything with a coin is to use a clean install of windows 7 although I have yet to do extensive testing of the latest photon wallet on windows 10. Other members of the blake coin team find the current builds of blake coin and children have been working ok on windows 10 personally I have no desire to use this operating system prefering linux. Honestly while this is not at all related to building coin wallets or software development i cannot urge you to move away from windows to linux as much as possible , it is free, open source, easy as windows or osx to use and while there is no guarantee you won't get hacked (on any system) the future of linux as an open environment is certain to be supported although based on the research of many people the 'unstability' and 'other security issues' that have been noted with windows ten are too many to mention.
  6. new release -- likely last release of 2015 --- Photon 8.9.6 Thanks to Blue Dragon 747 Bugfixes to codebase Wallet compiled with latest release of open ssl 1.0.2e Enjoy https://github.com/photonproject/photon/releases/tag/0.8.9.6a
  7. Ok, not sure what all the fuss is about , blockchain is 163581 tall , (and moving as I logged in to type this)-- these are the five peers I connected my wallet to within a minute of starting it. Note, the blocks downloaded slowly but took no more than ten minutes to synchronize up, my wallet was last open a few weeks ago, The proof of stake difficulty is "proof-of-stake" : 0.26484887 see here getblockhash 163585 0a7719adc0d73885768695e30264439fa27c1968f8f97145500dee90a1f72b40 { "hash" : "0a7719adc0d73885768695e30264439fa27c1968f8f97145500dee90a1f72b40", "confirmations" : 1, "size" : 454, "height" : 163585, "version" : 4, "merkleroot" : "eed79f6b3cf5dc3eb029e34cde793d89205f7e3b02f6d513d945f2c121921801", "mint" : 20.40000000, "time" : 1442618082, "nonce" : 0, "bits" : "1d03a797", "difficulty" : 0.27362000, "previousblockhash" : "1859e1c9702201111d51c7627146fef48b82985231103290aa633096994b9f2f", "flags" : "proof-of-stake", "proofhash" : "000086d990fca814750b494f9899cd69d0ea4198e9841e69d56ac76f850c4502", "entropybit" : 0, "modifier" : "43677a57a64482cc", "modifierchecksum" : "ca22cda0", "tx" : [ "674d75e5f9a38bbcd2c9aacea9c8fb8ede10e809172d8b5f562bba9f74445321", "be2e2a4544d68a7f3d7d45d400c20079ac4fad8fdcdf7b9c1f12b0e86d6cfe9f" ], "signature" : "30440220477ad143750d75332bcb7b5c9d8f0f8b0f17b5810a4ddcc442663ba0e850f324022072a571687b336aa269888c63df86a67b7533c8c59f9ce4bac373b391c5de54d6" } 68.148.28.13:50272 68.9.193.168:58184 184.90.7.112:43226 188.165.2.147:32955 104.14.181.24:2382 hopefully this information is helpful --- the codebase of Blade is quite old , however at a quick glance it appears to be functioning normally -- if anyone has different hashes or signatures ect.... for this same block height please post them here , that would indicate multiple chains however I probed 'out there' for multiple chains and could not connect to any ...... Have a pleasant weekend all .... please remember to set noirc=1 in your conf file, if you are connecting and disconecting this obsolete code could be part of the problem depending on how you are configured and connecting to the web.
  8. Congratulations Jimmy on keeping things together in a world and subject that has a large tendancy to attract chaos. I don't get to check in as often as I used to but the forum has outlasted many many other things. I hope it remains forever, even if 100 years from now to be in someones wayback machine so all the excitement many of us had here and may still have can be relived by someone , someday. And yes, there have been many exciting times in the forum. Who could forget ninja launches of new coins without wallets and someone saving the day by building one, who can forget the long threads where some developers argue with other developers on their team about control of a particular project or coin ...... and all the other dramatics..... Oh my what fun , and we continue ......................... Or should I say, those of you who have lasted this long realize there is more to crypto currency than plugging in a gpu and having it be the same a money printing press..... never worked that way and never will. And still i think we have lurkers and new comers to the forum. I sure as hell lurked for months before i ever joined. Just like other things. Ok I now leave memory lane and urge you on to the future and your regularly scheduled program. (just for old times.... NO I WILL NOT MAKE A COIN FOR YOU )
  9. Well not sure how the massive relaunch was lol but the codebase was long ago updated to be equal with bitcoin 9.2 ,9.3 and 9.4 depending on which features you use for evaluation, but we call it ix 9.3 about 90% of the coding was done by Ahmed Bodi, with a dev who i think works on annonacoin named Groundrod helping out (very knnowledgable fellow) I may have made one or two minor contributions and of course was left to building the windows wallets for release (i guess my specialty) Since then more recently one of the tech people from f2 pool (or so i believe he is ) named Wang Chun did a pull request i merged with a few minor but very important fixes that were causing issues for people trying to merge mine ix coin 9.3 with namecoin and bitcoin and the others...... The most current development tree is housed on Vlad Roberto's github here https://github.com/vladroberto/IXCoin the latest wallet release for windows is here https://github.com/vladroberto/IXCoin/releases/tag/0.9.3.a note the repository is one commit ahead (a protocol bump) that I am likely to revert if building on linux or osx suggest you revert my last commit also that windows release of ix coin , ix coind and ixcoin-cli are based on the earlier version of the repo, see the comments i placed on github for more details, you may need a few add nodes if it won't connect out of the box perhaps these ? addnode=24.34.40.175 addnode=142.4.208.71 addnode=24.42.148.53 addnode=184.78.215.89 addnode=62.75.167.48 addnode=83.163.120.176 addnode=123.203.84.34 addnode=86.93.208.193 addnode=2.29.136.165:8337 server=1 rpcuser=try to think of something unique and random rpcpassword= try to think of something unique and random server=1 listen=1 daemon=1 addnode=109.145.47.15 addnode=85.25.213.103 addnode=158.222.168.97 addnode=101.98.161.9 addnode=69.207.6.135 addnode=108.170.37.114 addnode=78.46.88.136:8337 addnode=80.74.157.31:8337 addnode=188.138.106.130:8337 addnode=80.74.157.31:8337 addnode=68.168.104.10:8337 addnode=198.50.239.11:8337 addnode=213.136.75.175:8337 addnode=118.244.207.8:8337 addnode=64.156.193.100:8337 addnode=188.165.82.228:8337 addnode=188.138.106.130:8337 addnode=80.74.157.31:8337
  10. actually , not so hard to solo mine with antminer or other sha asic units that only accept typically 3 pool entries for you to mine although technically it is not solomining (the solution) you create your own pool !! if you are only mining one coin and are not paying anything out to anyone it is actually not that difficult and you do not need a large server or cloud service to do it, can be done right in your living room, then you point the s1 at your local pool maybe something like 192.168.1.1 or whatever it's local ip is on your router and bang you got it !! there are guides on this forum how to set up your own pool, hell i was able to learn to do it long ago just from following the build directions on github for various pool software i guess mpos is the most popular now, it has a few holes/bugs that are pretty bad if not patched (like people being able to burn you for double payouts with auto payout and manual lol) but if you are the pools only member and you never let your friends sign up it becomes quite simple to point all the hash you want at your private pool, just keep in mind you need to run a full node of whatever coin you are planning to mine behind this and (i mention this only because i have observed it ) with some coins when you run a node (especially with sha 2 and scrypt 1024 coins since people suspect there may be some hash power around) if you keep that node open long enough depending on the coin someone may eventually 'snoop' around and try to connect to you and probe you with the hope of 'getting in' and taking over your hash power to direct it elsewhere or just steal coins..... not that i want to scare people off from trying to experiment, just keep good security proceedures in place, after your node is running well and your pool is mining in private you may want to consider running 'coind' with listen=0 if i recall most of the pool source code on github have some discussion in the docs and issues /pr's ect that describe some security measures..... have fun
  11. /*/ Good to hear the new wallet is working well for others. Was difficult for me to test it since i only have a fairly small amount of blade. Since i still have github privliges to update the coin i felt it was 'due'. Honestly it was a minor update but one thing about proof of stake coins (in particular this codebase and what blade is based on ) without fairly regular updates you can expect issues, those stake modifier checkpoints make a big difference it seems. What it could really use would be any /all the following 1) update to newer codebase using level db or and (maybe protofuf too !! to go all the way) 2) coin control similar to latest litecoin/bitcoin builds where you can select inputs as an expert feature (note- i think #1 has to come first since all the other projects i have done work on including the blake coin system of coins have coin control and need level db, also ixcoin has coin control in the 9.3 version have been maintaining and like bitcoin uses level db and protobuf) 3) more support ! blade enjoys many fans and strong supporters and bagholders and is traded on at leasat one exchange I believe but in a sea of proof of stake alt coins that promise many features (most of which are never delivered and just scams) blade is actually what i think a pretty honest project. I think there are a few major bagholders of blade but that does not make it a 'scam'.... funny how honest /non scam coins do not gain widespread acceptance just by functioning and doing what they are supossed to do and others projects do the opposite and get tagged 'short term' anyway, the bitcoin killer !! lol Finally to all using blade for best network results and to minimize the orphans ect if you have 100k blade and do not connect to the network for a few months you should expect to start block production up pretty quickly which in turn causes the client to freeze up. There is one very simple thing you need to do to prevent this no matter how many coins you have and no matter how long they were sitting .... in your conf file set reservebalance=x where x is a number no more than the difference of 5% of your total coins if you hold over 50k in the wallet if you have say only 5-10 k you can go to 10% so for example , if you own 200,000 coins , 5 percent of this is 10,000 coins, (.05x200000= 10000) you would use the line reservebalance=190000 and there it is , it will only allow 10,000 of your coins to 'stake' at one time instead of all of them screaming at the network, you will still earn over even just a few days the exact same amount of coins and the network will stay much more stable !! one final thing, for smooth operation of blade it still has irc code in it, that is another thing that needs to be taken out put the line noirc=1 in your conf always, enjoy --- it is honestly refreshing to hear something 'positive' once and a while vs. the normal muttering in the world of cryptocurrency thank you jojojo / */
  12. Small update to guide , did not add to main page but I may in the future Photon now uses the latest version of openssl which as of now is 1.0.2d so OPENSSL_LIB_PATH=C:\deps\openssl-1.0.1j becomes OPENSSL_LIB_PATH=C:\deps\openssl-1.0.2d when building open ssl for any coin I highly recommend this method in msys shell on win cd /c/deps/ tar xvfz openssl-1.0.2d.tar.gz cd openssl-1.0.2d ./Configure no-zlib no-shared no-dso no-krb5 no-camellia no-capieng no-cast no-cms no-dtls1 no-gost no-gmp no-heartbeats no-idea no-jpake no-md2 no-mdc2 no-rc5 no-rdrand no-rfc3779 no-rsax no-sctp no-seed no-sha0 no-static_engine no-whirlpool no-rc2 no-rc4 no-ssl2 no-ssl3 mingw make depend make also if you prefer to use mingw 48 install this version http://sourceforge.net/projects/mingw/files/Installer/mingw-get-setup.exe/download you need msys-base.bin if using this version of mingw i suggest this copy of gcc http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win32/Personal%20Builds/mingw-builds/4.8.2/threads-posix/dwarf/i686-4.8.2-release-posix-dwarf-rt_v3-rev2.7z/download unzip it to c:\ or your root drive and copy it to your mingw folder more to follow when i have some additional time
  13. Photon 0.8.9.5 has been released Upgrades to security to prevent consensus forks from different /outdated versions of open-ssl The qt and daemon for windows are here https://github.com/photonproject/photon/releases/tag/0.8.9.5 Thanks to everyone who continues to support the Blake256 network. Many things are in the works.
  14. Mac wallets are not supported for now. If you want to you can build yourself if you like I will teach you how......... I believe you will need these patches to the source code of photon https://github.com/photonproject/photon/commit/e56ff2c291f94ec3d632c26ab15d53ae58e3e439 https://github.com/photonproject/photon/commit/0067cf2b070679f276ccc283f4316cc2ca43b5b7 then install mac ports if you don't have it (may conflict if you have homebrew installed) https://www.macports.org/install.php from terrminal run .... sudo port install autoconf pkgconfig automake boost qt4-mac db48 openssl miniupnpc qrencode git clone the master repo and apply the patches above pro file needs windows items commented out or removed if not allready done and these should be up top BDB_INCLUDE_PATH=/opt/local/include/db48 BDB_LIB_PATH=/opt/local/lib/db48 BOOST_INCLUDE_PATH=/opt/local/include/boost BOOST_LIB_PATH=/opt/local/lib MINIUPNPC_INCLUDE_PATH=/opt/local/include/miniupnpc MINIUPNPC_LIB_PATH=/opt/local/lib OPENSSL_INCLUDE_PATH=/opt/local/include/openssl OPENSSL_LIB_PATH=/opt/local/lib QRENCODE_INCLUDE_PATH=/opt/local/include QRENCODE_LIB_PATH=/opt/local/lib from terminal you can finish the job from the photon dir qmake USE_QRCODE=1 make you can also open qt creator and build from it directly (i prefer this method) Mac's are not supported for several reasons honestly if you are using a mac the best advice i can give you is to (change computers--- only kidding) install virtual box and either install linux (desktop or command line if you are up for it) or go to microsoft's website and download an iso image of windows 7 and install windows 7 in virtual box. Another thing unrelated to Photon about macs --- I have discovered it is actually impossible to turn off or disable the microphone on a mac..... no joke, if anyone finds a method that will not require me to take it apart or put a piece of chewing gum on the mic.... pm me if you please..... (ive looked and asked others, many people have failed to actually really turn it off) on command line
  15. you will likely run out of memory also if you do not set a swap file maybe something like sudo fallocate -l 4G /swapfile4G sudo mkswap /swapfile4G sudo swapon /swapfile4G sudo swapoff /swapfile sudo rm /swapfile sudo swapon -s