#like no let me fill in a solid color without the transparent dots

[lyss-butterscotch]

Hey @ressioo remember when you said suns undertale?

[suzanneshannon]

Stacked “Borders”

A little while back, I was in the process of adding focus styles to An Event Apart’s web site. Part of that was applying different focus effects in different areas of the design, like white rings in the header and footer and orange rings in the main text. But in one place, I wanted rings that were more obvious—something like stacking two borders on top of each other, in order to create unusual shapes that would catch the eye.

I toyed with the idea of nesting elements with borders and some negative margins to pull one border on top of another, or nesting a border inside an outline and then using negative margins to keep from throwing off the layout. But none of that felt satisfying.

It turns out there are a number of tricks to create the effect of stacking one border atop another by combining a border with some other CSS effects, or even without actually requiring the use of any borders at all. Let’s explore, shall we?

Outline and box-shadow

If the thing to be multi-bordered is a rectangle—you know, like pretty much all block elements—then mixing an outline and a spread-out hard box shadow may be just the thing.

Let’s start with the box shadow. You’re probably used to box shadows like this:

.drop-me { background: #AEA; box-shadow: 10px 12px 0.5rem rgba(0,0,0,0.5); }

That gets you a blurred shadow below and to the right of the element. Drop shadows, so last millennium! But there’s room, and support, for a fourth length value in box-shadow that defines a spread distance. This increases the size of the shadow’s shape in all directions by the given length, and then it’s blurred. Assuming there’s a blur, that is.

So if we give a box shadow no offset, no blur, and a bit of spread, it will draw itself all around the element, looking like a solid border without actually being a border.

.boxborder-me { box-shadow: 0 0 0 5px firebrick; }

This box-shadow "border" is being drawn just outside the outer border edge of the element. That’s the same place outlines get drawn around block boxes, so all we have to do now is draw an outline over the shadow. Something like this:

.boxborder-me { box-shadow: 0 0 0 5px firebrick; outline: dashed 5px darkturquoise; }

Bingo. A multicolor "border" that, in this case, doesn’t even throw off layout size, because shadows and outlines are drawn after element size is computed. The outline, which sits on top, can use pretty much any outline style, which is the same as the list of border styles. Thus, dotted and double outlines are possibilities. (So are all the other styles, but they don’t have any transparent parts, so the solid shadow could only be seen through translucent colors.)

If you want a three-tone effect in the border, multiple box shadows can be created using a comma-separated list, and then an outline put over top that. For example:

.boxborder-me { box-shadow: 0 0 0 1px darkturquoise, 0 0 0 3px firebrick, 0 0 0 5px orange, 0 0 0 6px darkturquoise; outline: dashed 6px darkturquoise; }

Taking it back to simpler effects, combining a dashed outline over a spread box shadow with a solid border of the same color as the box shadow creates yet another effect:

.boxborder-me { box-shadow: 0 0 0 5px firebrick; outline: dashed 5px darkturquoise; border: solid 5px darkturquoise; }

The extra bonus here is that even though a box shadow is being used, it doesn’t fill in the element’s background, so you can see the backdrop through it. This is how box shadows always behave: they are only drawn outside the outer border edge. The "rest of the shadow," the part you may assume is always behind the element, doesn’t exist. It’s never drawn. So you get results like this:

This is the result of explicit language in the CSS Background and Borders Module, Level 3, section 7.1.1:

An outer box-shadow casts a shadow as if the border-box of the element were opaque. Assuming a spread distance of zero, its perimeter has the exact same size and shape as the border box. The shadow is drawn outside the border edge only: it is clipped inside the border-box of the element.

(Emphasis added.)

Border and box-shadow

Speaking of borders, maybe there’s a way to combine borders and box shadows. After all, box shadows can be more than just drop shadows. They can also be inset. So what if we turned the previous shadow inward, and dropped a border over top of it?

.boxborder-me { box-shadow: 0 0 0 5px firebrick inset; border: dashed 5px darkturquoise; }

That’s... not what we were after. But this is how inset shadows work: they are drawn inside the outer padding edge (also known as the inner border edge), and clipped beyond that:

An inner box-shadow casts a shadow as if everything outside the padding edge were opaque. Assuming a spread distance of zero, its perimeter has the exact same size and shape as the padding box. The shadow is drawn inside the padding edge only: it is clipped outside the padding box of the element.

(Ibid; emphasis added.)

So we can’t stack a border on top of an inset box-shadow. Maybe we could stack a border on top of something else...?

Border and multiple backgrounds

Inset shadows may be restricted to the outer padding edge, but backgrounds are not. An element’s background will, by default, fill the area out to the outer border edge. Fill an element background with solid color, give it a thick dashed border, and you’ll see the background color between the visible pieces of the border.

So what if we stack some backgrounds on top of each other, and thus draw the solid color we want behind the border? Here’s step one:

.multibg-me { border: 5px dashed firebrick; background: linear-gradient(to right, darkturquoise, 5px, transparent 5px); background-origin: border-box; }

We can see, there on the left side, the blue background visible through the transparent parts of the dashed red border. Add three more like that, one for each edge of the element box, and:

.multibg-me { border: 5px dashed firebrick; background: linear-gradient(to top, darkturquoise, 5px, transparent 5px), linear-gradient(to right, darkturquoise, 5px, transparent 5px), linear-gradient(to bottom, darkturquoise, 5px, transparent 5px), linear-gradient(to left, darkturquoise, 5px, transparent 5px); background-origin: border-box; }

In each case, the background gradient runs for five pixels as a solid dark turquoise background, and then has a color stop which transitions instantly to transparent. This lets the "backdrop" show through the element while still giving us a "stacked border."

One major advantage here is that we aren’t limited to solid linear gradients—we can use any gradient of any complexity, just to spice things up a bit. Take this example, where the dashed border has been made mostly transparent so we can see the four different gradients in their entirety:

.multibg-me { border: 15px dashed rgba(128,0,0,0.1); background: linear-gradient(to top, darkturquoise, red 15px, transparent 15px), linear-gradient(to right, darkturquoise, red 15px, transparent 15px), linear-gradient(to bottom, darkturquoise, red 15px, transparent 15px), linear-gradient(to left, darkturquoise, red 15px, transparent 15px); background-origin: border-box; }

If you look at the corners, you’ll see that the background gradients are rectangular, and overlap each other. They don’t meet up neatly, the way border corners do. This can be a problem if your border has transparent parts in the corners, as would be the case with border-style: double. Also, if you just want a solid color behind the border, this is a fairly clumsy way to stitch together that effect. Surely there must be a better approach?

Border and background clipping

Yes, there is! It involves changing the clipping boxes for two different layers of the element’s background. The first thing that might spring to mind is something like this:

.multibg-me { border: 5px dashed firebrick; background: #EEE, darkturquoise; background-clip: padding-box, border-box; }

But that does not work, because CSS requires that only the last (and thus lowest) background be set to a <color> value. Any other background layer must be an image.

So we replace that very-light-gray background color with a gradient from that color to that color: this works because gradients are images. In other words:

.multibg-me { border: 5px dashed firebrickred; background: linear-gradient(to top, #EEE, #EEE), darkturquoise; background-clip: padding-box, border-box; }

The light gray "gradient" fills the entire background area, but is clipped to the padding box using background-clip. The dark turquoise fills the entire area and is clipped to the border box, as backgrounds always have been by default. We can alter the gradient colors and direction to anything we like, creating an actual visible gradient or shifting it to all-white or whatever other linear effect we would like.

The downside here is that there’s no way to make that padding-area background transparent such that the element’s backdrop can be seen through the element. If the linear gradient is made transparent, then the whole element background will be filled with dark turquoise. Or, more precisely, we’ll be able to see the dark turquoise that was always there.

In a lot of cases, it won’t matter that the element background isn‘t see-through, but it’s still a frustrating limitation. Isn’t there any way to get the effect of stacked borders without wacky hacks and lost capabilities?

Border images

In fact, what if we could take an image of the stacked border we want to see in the world, slice it up, and use that as the border? Like, say, this image becomes this border?

Here’s the code to do exactly that:

.borderimage-me { border: solid 5px; border-image: url(triple-stack-border.gif) 15 / 15px round; }

First, we set a solid border with some width. We could also set a color for fallback purposes, but it’s not really necessary. Then we point to an image URL, define the slice inset(s) at 15 and width of the border to be 15px, and finally the repeat pattern of round.

There are more options for border images, which are a little too complex to get into here, but the upshot is that you can take an image, define nine slices of it using offset values, and have those images used to synthesize a complete border around an image. That’s done by defining offsets from the edges of the image itself, which in this case is 15. Since the image is a GIF and thus pixel-based, the offsets are in pixels, so the "slice lines" are set 15 pixels inward from the edges of the image. (In the case of an SVG, the offsets are measured in terms of the SVG’s coordinate system.) It looks like this:

Each slice is assigned to the corner or side of the element box that corresponds to itself; i.e., the bottom right corner slice is placed in the bottom right corner of the element, the top (center) slice is used along the top edge of the element, and so on.

If one of the edge slices is smaller than the edge of the element is long—which almost always happens, and is certainly true here—then the slice is repeated in one of a number of ways. I chose round, which fills in as many repeats as it can and then scales them all up just enough to fill out the edge. So with a 70-pixel-long slice, if the edge is 1,337 pixels long, there will be 19 repetitions of the slice, each of which is scaled to be 70.3 pixels wide. Or, more likely, the browser generates a single image containing 19 repetitions that’s 1,330 pixels wide, and then stretches that image the extra 7 pixels.

You might think the drawback here is browser support, but that turns out not to be the case.

This browser support data is from Caniuse, which has more detail. A number indicates that browser supports the feature at that version and up.

Desktop

ChromeOperaFirefoxIEEdgeSafari56435011129.1

Mobile / Tablet

iOS SafariOpera MobileOpera MiniAndroidAndroid ChromeAndroid Firefox9.346all*677164

Just watch out for the few bugs (really, implementation limits) that linger around a couple of implementations, and you’ll be fine.

Conclusion

While it might be a rare circumstance where you want to combine multiple "border" effects, or stack them atop each other, it’s good to know that CSS provides a number of ways to get the job done, and that most of them are already widely supported. And who knows? Maybe one day there will be a simple way to achieve these kinds of effects through a single property, instead of by mixing several together. Until then, happy border stacking!

The post Stacked “Borders” appeared first on CSS-Tricks.

Stacked “Borders” published first on https://deskbysnafu.tumblr.com/

[siliconwebx]

Stacked “Borders”

A little while back, I was in the process of adding focus styles to An Event Apart’s web site. Part of that was applying different focus effects in different areas of the design, like white rings in the header and footer and orange rings in the main text. But in one place, I wanted rings that were more obvious—something like stacking two borders on top of each other, in order to create unusual shapes that would catch the eye.

I toyed with the idea of nesting elements with borders and some negative margins to pull one border on top of another, or nesting a border inside an outline and then using negative margins to keep from throwing off the layout. But none of that felt satisfying.

It turns out there are a number of tricks to create the effect of stacking one border atop another by combining a border with some other CSS effects, or even without actually requiring the use of any borders at all. Let’s explore, shall we?

Outline and box-shadow

If the thing to be multi-bordered is a rectangle—you know, like pretty much all block elements—then mixing an outline and a spread-out hard box shadow may be just the thing.

Let’s start with the box shadow. You’re probably used to box shadows like this:

.drop-me { background: #AEA; box-shadow: 10px 12px 0.5rem rgba(0,0,0,0.5); }

That gets you a blurred shadow below and to the right of the element. Drop shadows, so last millennium! But there’s room, and support, for a fourth length value in box-shadow that defines a spread distance. This increases the size of the shadow’s shape in all directions by the given length, and then it’s blurred. Assuming there’s a blur, that is.

So if we give a box shadow no offset, no blur, and a bit of spread, it will draw itself all around the element, looking like a solid border without actually being a border.

.boxborder-me { box-shadow: 0 0 0 5px firebrick; }

This box-shadow "border" is being drawn just outside the outer border edge of the element. That’s the same place outlines get drawn around block boxes, so all we have to do now is draw an outline over the shadow. Something like this:

.boxborder-me { box-shadow: 0 0 0 5px firebrick; outline: dashed 5px darkturquoise; }

Bingo. A multicolor "border" that, in this case, doesn’t even throw off layout size, because shadows and outlines are drawn after element size is computed. The outline, which sits on top, can use pretty much any outline style, which is the same as the list of border styles. Thus, dotted and double outlines are possibilities. (So are all the other styles, but they don’t have any transparent parts, so the solid shadow could only be seen through translucent colors.)

If you want a three-tone effect in the border, multiple box shadows can be created using a comma-separated list, and then an outline put over top that. For example:

.boxborder-me { box-shadow: 0 0 0 1px darkturquoise, 0 0 0 3px firebrick, 0 0 0 5px orange, 0 0 0 6px darkturquoise; outline: dashed 6px darkturquoise; }

Taking it back to simpler effects, combining a dashed outline over a spread box shadow with a solid border of the same color as the box shadow creates yet another effect:

.boxborder-me { box-shadow: 0 0 0 5px firebrick; outline: dashed 5px darkturquoise; border: solid 5px darkturquoise; }

The extra bonus here is that even though a box shadow is being used, it doesn’t fill in the element’s background, so you can see the backdrop through it. This is how box shadows always behave: they are only drawn outside the outer border edge. The "rest of the shadow," the part you may assume is always behind the element, doesn’t exist. It’s never drawn. So you get results like this:

This is the result of explicit language in the CSS Background and Borders Module, Level 3, section 7.1.1:

An outer box-shadow casts a shadow as if the border-box of the element were opaque. Assuming a spread distance of zero, its perimeter has the exact same size and shape as the border box. The shadow is drawn outside the border edge only: it is clipped inside the border-box of the element.

(Emphasis added.)

Border and box-shadow

Speaking of borders, maybe there’s a way to combine borders and box shadows. After all, box shadows can be more than just drop shadows. They can also be inset. So what if we turned the previous shadow inward, and dropped a border over top of it?

.boxborder-me { box-shadow: 0 0 0 5px firebrick inset; border: dashed 5px darkturquoise; }

That’s... not what we were after. But this is how inset shadows work: they are drawn inside the outer padding edge (also known as the inner border edge), and clipped beyond that:

An inner box-shadow casts a shadow as if everything outside the padding edge were opaque. Assuming a spread distance of zero, its perimeter has the exact same size and shape as the padding box. The shadow is drawn inside the padding edge only: it is clipped outside the padding box of the element.

(Ibid; emphasis added.)

So we can’t stack a border on top of an inset box-shadow. Maybe we could stack a border on top of something else...?

Border and multiple backgrounds

Inset shadows may be restricted to the outer padding edge, but backgrounds are not. An element’s background will, by default, fill the area out to the outer border edge. Fill an element background with solid color, give it a thick dashed border, and you’ll see the background color between the visible pieces of the border.

So what if we stack some backgrounds on top of each other, and thus draw the solid color we want behind the border? Here’s step one:

.multibg-me { border: 5px dashed firebrick; background: linear-gradient(to right, darkturquoise, 5px, transparent 5px); background-origin: border-box; }

We can see, there on the left side, the blue background visible through the transparent parts of the dashed red border. Add three more like that, one for each edge of the element box, and:

.multibg-me { border: 5px dashed firebrick; background: linear-gradient(to top, darkturquoise, 5px, transparent 5px), linear-gradient(to right, darkturquoise, 5px, transparent 5px), linear-gradient(to bottom, darkturquoise, 5px, transparent 5px), linear-gradient(to left, darkturquoise, 5px, transparent 5px); background-origin: border-box; }

In each case, the background gradient runs for five pixels as a solid dark turquoise background, and then has a color stop which transitions instantly to transparent. This lets the "backdrop" show through the element while still giving us a "stacked border."

One major advantage here is that we aren’t limited to solid linear gradients—we can use any gradient of any complexity, just to spice things up a bit. Take this example, where the dashed border has been made mostly transparent so we can see the four different gradients in their entirety:

.multibg-me { border: 15px dashed rgba(128,0,0,0.1); background: linear-gradient(to top, darkturquoise, red 15px, transparent 15px), linear-gradient(to right, darkturquoise, red 15px, transparent 15px), linear-gradient(to bottom, darkturquoise, red 15px, transparent 15px), linear-gradient(to left, darkturquoise, red 15px, transparent 15px); background-origin: border-box; }

If you look at the corners, you’ll see that the background gradients are rectangular, and overlap each other. They don’t meet up neatly, the way border corners do. This can be a problem if your border has transparent parts in the corners, as would be the case with border-style: double. Also, if you just want a solid color behind the border, this is a fairly clumsy way to stitch together that effect. Surely there must be a better approach?

Border and background clipping

Yes, there is! It involves changing the clipping boxes for two different layers of the element’s background. The first thing that might spring to mind is something like this:

.multibg-me { border: 5px dashed firebrick; background: #EEE, darkturquoise; background-clip: padding-box, border-box; }

But that does not work, because CSS requires that only the last (and thus lowest) background be set to a <color> value. Any other background layer must be an image.

So we replace that very-light-gray background color with a gradient from that color to that color: this works because gradients are images. In other words:

.multibg-me { border: 5px dashed firebrickred; background: linear-gradient(to top, #EEE, #EEE), darkturquoise; background-clip: padding-box, border-box; }

The light gray "gradient" fills the entire background area, but is clipped to the padding box using background-clip. The dark turquoise fills the entire area and is clipped to the border box, as backgrounds always have been by default. We can alter the gradient colors and direction to anything we like, creating an actual visible gradient or shifting it to all-white or whatever other linear effect we would like.

The downside here is that there’s no way to make that padding-area background transparent such that the element’s backdrop can be seen through the element. If the linear gradient is made transparent, then the whole element background will be filled with dark turquoise. Or, more precisely, we’ll be able to see the dark turquoise that was always there.

In a lot of cases, it won’t matter that the element background isn‘t see-through, but it’s still a frustrating limitation. Isn’t there any way to get the effect of stacked borders without wacky hacks and lost capabilities?

Border images

In fact, what if we could take an image of the stacked border we want to see in the world, slice it up, and use that as the border? Like, say, this image becomes this border?

Here’s the code to do exactly that:

.borderimage-me { border: solid 5px; border-image: url(triple-stack-border.gif) 15 / 15px round; }

First, we set a solid border with some width. We could also set a color for fallback purposes, but it’s not really necessary. Then we point to an image URL, define the slice inset(s) at 15 and width of the border to be 15px, and finally the repeat pattern of round.

There are more options for border images, which are a little too complex to get into here, but the upshot is that you can take an image, define nine slices of it using offset values, and have those images used to synthesize a complete border around an image. That’s done by defining offsets from the edges of the image itself, which in this case is 15. Since the image is a GIF and thus pixel-based, the offsets are in pixels, so the "slice lines" are set 15 pixels inward from the edges of the image. (In the case of an SVG, the offsets are measured in terms of the SVG’s coordinate system.) It looks like this:

Each slice is assigned to the corner or side of the element box that corresponds to itself; i.e., the bottom right corner slice is placed in the bottom right corner of the element, the top (center) slice is used along the top edge of the element, and so on.

If one of the edge slices is smaller than the edge of the element is long—which almost always happens, and is certainly true here—then the slice is repeated in one of a number of ways. I chose round, which fills in as many repeats as it can and then scales them all up just enough to fill out the edge. So with a 70-pixel-long slice, if the edge is 1,337 pixels long, there will be 19 repetitions of the slice, each of which is scaled to be 70.3 pixels wide. Or, more likely, the browser generates a single image containing 19 repetitions that’s 1,330 pixels wide, and then stretches that image the extra 7 pixels.

You might think the drawback here is browser support, but that turns out not to be the case.

This browser support data is from Caniuse, which has more detail. A number indicates that browser supports the feature at that version and up.

Desktop

ChromeOperaFirefoxIEEdgeSafari56435011129.1

Mobile / Tablet

iOS SafariOpera MobileOpera MiniAndroidAndroid ChromeAndroid Firefox9.346all*677164

Just watch out for the few bugs (really, implementation limits) that linger around a couple of implementations, and you’ll be fine.

Conclusion

While it might be a rare circumstance where you want to combine multiple "border" effects, or stack them atop each other, it’s good to know that CSS provides a number of ways to get the job done, and that most of them are already widely supported. And who knows? Maybe one day there will be a simple way to achieve these kinds of effects through a single property, instead of by mixing several together. Until then, happy border stacking!

The post Stacked “Borders” appeared first on CSS-Tricks.

😉SiliconWebX | 🌐CSS-Tricks

[smartoptionsio]

Steve’s 2019 Portfolio – Some Classics & Some Crypto 2.0 Coins/Tokens

WebFont.load({ google: { families: ['Merriweather'] } }); #colorbox_main_container_7681 .wpsm_panel { margin-bottom: 0px !important; background-color: #ffffff; border: 1px solid #cccccc; border-radius: 1px; -webkit-box-shadow:3px 3px 15px 0px #000000; box-shadow:3px 3px 15px 0px #000000; -moz-box-shadow:3px 3px 15px 0px #000000; } #colorbox_main_container_7681 .wpsm_panel-default > .wpsm_panel-heading { background-color: #ffffff !important; border-color: rgba(0,0,0,0.05); border-top-left-radius: 0px; border-top-right-radius: 0px; border-top-left-radius: 1px; border-top-right-radius: 1px; text-align:center !important; padding:14px 15px !important; } #colorbox_main_container_7681 .colorbox_singel_box{ margin-bottom:20px !important; padding-top: 5px; } #colorbox_main_container_7681 .wpsm_panel-title{ margin-top: 0 !important; margin-bottom: 0 !important; font-size: 18px !important; color: #000000 !important; font-family: Merriweather !important; word-wrap:break-word; text-align:center !important; padding: 0px !important; line-height:1.5 !important; } #colorbox_main_container_7681 .wpsm_panel-title span{ font-size: 25px !important; color: #000000 !important; vertical-align: middle; display:inline-block !important; } #colorbox_main_container_7681 .wpsm_panel-title a{ padding:0px !important; margin:0px !important; text-decoration:none !important; outline:none !important; border:0px !important; } #colorbox_main_container_7681 .wpsm_panel-title a:hover{ color: #000000 !important; } #colorbox_main_container_7681 .wpsm_panel-body{ color: #000000 !important; background-color:#ffffff !important; font-size:16px !important; font-family: Merriweather !important; overflow:hidden; text-align:left!important; line-height:1.5 !important; border-bottom-left-radius: 1px; border-bottom-right-radius: 1px; } #colorbox_main_container_7681 .wpsm_panel-heading { background-image: none !important; } @media (max-width: 992px){ .colorbox_singel_box{ width:50% !important; } } @media (max-width: 786px){ .colorbox_singel_box{ width:100% !important; } }

Disclaimer

This article is for educational purposes only. We are no financial advisors. Do not make investment decisions based on this informations. The information provided from Smart Options is for informational purposes only. It should not be considered legal or financial advice. You should consult with a financial advisor or other professional to find out what may be best for your individual needs and risk tolerance. Please do your own research and let never anyone trade for you. Please read this disclaimer and leave the website if you disagree with it.

new AnimOnScroll( document.getElementById( 'colorbox_main_container_7681' ), { minDuration : 0.4, maxDuration : 0.7, viewportFactor : 0.1 } );

My Telegram became pretty busy this year (thank you guys, I appreciate your messages!) and my goal is it to tackle two of the most requested postings I received within the last days of this year: 1. of course the best Crypto Signal Auto Traders (likely the next post I will release. Hopefully, I can make it in ’18) and 2. which Portfolio I prepared for the long term. This is a relative light-weight one and I will be completely transparent on this one. In March, I accepted the bear market to be a long lasting one and sold the altcoin portfolios I held until then in a painful loss. Furthermore, I realized that some of my old favorites prolly might have become outdated in these times and I focused on fresher coins and tokens. Projects that learned from the mistakes of the 1.0 generation, projects that didn’t start with a gazillion of crowdfunded ETH. coming from the ICO frenzy or by VCs (and therefore never can act really free). However, I re-bought some major coins, which are pretty obvious and are likely here to stay – they are included in this portfolio.

2017 has shown how important it is to become disillusioned. “Disillusioned”, a word many might perceive as negative. To me, it is rather positive as it can’t be wrong to break free from misleading illusions and put a pragmatism, realistic outlook in place. The crypto clearing is not yet done. Shitcoin companies have to die. The projects founded in this bear market & maintained/developed throughout this bear market – these might have a chance to become the winners. Remember the dot-com bubble, the majority of companies imploded – but what happened to the true visionaries? What happened to the folks that worked for months without any notable income but with a strong vision and goal? And, most importantly, where are they now?

The Light-Weight Steve McKenzie Crypto Portfolio

Bitcoin 30%

Until there are major sentiments of changes in Bitcoin, I will always keep this 30 %, the majority of my portfolio in Bitcoin. I don’t think it needs further explanation – Bitcoin is the market leader in crypto and I suspect it to remain in this position within the next years. We have the Lightning Network and many other great things to come on a broad scale and I firmly believe that mass adoption will start in BTC.

Current Price:  Exchange: Binance

ETH 10%

Well, yeah – there was a big ICO sell-off, and I don’t want to know what big ICOs like EOS have still on the stack to sell it off. But I think it is still a major groundbreaking tech for the blockchain and the smart contract platform, which ETH actually offers, has more to provide than just the ICO purpose. Smart contracts will be a huge part of our future, this is my belief, and this is what ETH stands for. I am DCA’ing ETH, buying back a little fraction each Friday and  I believe we still can see lows like $70. ETH is also known for having fat fingers to appear. This means I placed some orders in the low double-digit and single-digit area, just for the case they might get filled with a quick flash crash.

Current Price:  Exchange: Binance

HOT 10%

Holochain is a fantastic project and could play a major role on the Internet 3.0. We need to get our data off the big centralized server farms onto decentralized mini units – the Holoports. The project comes without any VC funding and my first Holoport is currently on the way to me – collecting Holo Fuel to fulfill my dream of hosting SmartOptions one day in the near future on the blockchain, right in the tiny white box in your living room. To order your holoport click here, to get a basic understanding of the ingenious concept, watch the video below or read our article on Holo.

Current Price:  Exchange: Binance

XRP 10%

Ripple, I mean, it is Ripple – you don’t have to like it, you don’t have to support it – but you surely should hold a stack of ripple as a classic coin in your portfolio. Read the article “The Ripple Mafia” to learn how which mighty forces are involved and you will understand, they will never let this shitcoin die, but do everything humanly possible to increase its value. I mean they will do things like buying Bill Clinton as a speaker for their events and what else. Just hold a good portion of XRP.

Current Price:  Exchange: Binance

XLM 10%

Stellar is a silicon valley backed coin, also on of the older ones and a “classic coin”. Jed McCaleb, the founder of OpenCoin, Mt. Gox and eDonkey, left Ripple to set up Stellar that is currently sitting at $5 billion market cap.  Stellar is already 5 years on the market and do pretty well with partnerships in the field of IBM and the likes. Stellar is a platform that aims to connect people from around the world, whether rich or poor, with low-cost forms of payment and their own cryptocurrency $xlm. The team behind stellar.org is a motley team of top developers and finance personalities. The fight against poverty is paramount to them and as a nonprofit organization behind the project, they are appearing as the white knight in comparison to evil banker Ripple.

Current Price:  Exchange: Binance

XLQ 10%

The skyrocketing of the ALQO price found to an early end, though I still believe in this well-spread project. Especially with the Bitfineon launch ahead, which leaves a great impression, this masternode coin with privacy features is built to last. Actually, I planned only 5% for XLQ, but with the current prices, I couldn’t hold back and doubled up. I run multiple masternodes of ALQO right now and keep the same amount in the Liberio wallet for cold staking. The rewards dropping in are very nice and personally, I cannot wait for the launch of their fiat enabled exchange with XLQ as a base currency. Check out what they are going to launch very soon – and is not yet priced in! This is a quality exchange, not the shit we usually see.

Current Price: Exchange: Crypto Bridge

Poly 5%

Securities on the blockchain – well, that might become quite a thing. Polymath automates many processes to enable companies issuing security with the help of a standardized token protocol.

Current Price:  Exchange: Binance

BNB 5%

The market leader exchange and it is coin. Binance was always ahead of things, the token is used daily by millions of traders to reduce the fees, the regularly burn coins and there might be a few more use cases for BNB in the future with their DEX.  BNB should be considered for holding. IMO the upside is limited, but still, there is a good room for growth. I will always hold some for my own Binance trading activities, but I won’t be married to my BNB.

Current Price:  Exchange: Binance

NXPS 5%

PundiX is a solid project with a strong emphasis on creating real use cases. PundiX focuses on all kinds of commerce online and offline and might be a huge winner, once mass adoption kicks in.

Current Price: Exchange: Binance

ZIL 5%

We wrote already about ZIL – it comes with very much needed new features and a tech that is ahead of the many.  Ziliqa’s objective is to become one of the main platforms in the supply chain in the coming year. Beyond that, it wants to continue to advance blockchain technology and bring the latest scientific research to life in a useful and relevant way. With the mainnet coming in Q1 ’19 it will attract  Dapp developers who focus on different industries due to the advanced tech. In the long run, this might increase the demand for Zilliqa (ZIL).

Current Price:  Exchange: Binance

GIN coin (yet 0%)

For those who follow our posts, you know I want to get into GIN. However. the price just never came really down since I discovered it and I am still waiting for a drop to get in. GIN provides a very convenient and cheap platform to host masternodes and increases its popularity day by day.

Current Price:  Exchange: Crypto Bridge

The post Steve’s 2019 Portfolio – Some Classics & Some Crypto 2.0 Coins/Tokens appeared first on Smart Options.